Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings

Add Version Control Functionality to Application Architect

Status: Under Consideration
by Employee on ‎10-26-2009 03:17 PM
Suggestion from UA Team:  Add version control to entities and smart parts in AA for easier reintegration of customizations after upgrading.
Status: Under Consideration
Great comments. This is on the list for consideration. Thanks.
Comments
by Bronze Super Contributor RyanFarley
on ‎10-26-2009 07:09 PM
My thoughts are that they've made Application Architect so it is easy to work with source control. Using a source control system gives you versioning of files and much more.
by Gold Super Contributor RJLedger
on ‎10-29-2009 10:46 AM

Not everyone will implement an external version control system. Having a built in version number that we can use when creating a bundle would be a GREAT help.

 

I'd add having a "tag" that would tell you if the component is a Sage SalesLogix provided one or has been customized.

Just think.. You could build a bundle very quickly of ALL custom pieces just by specifying that you wanted all NON SalesLogix parts. The version info would let you quickly verify it the part  (SalesLogix and/or custom) is the "latest".

 

The version number (and tag) would need to be persistent  across projects  - NOT the way things are done in the Windows/LAN - so that no matter WHO or what company made the change it just increments.

by Bronze Elite Contributor
on ‎10-29-2009 11:01 AM
RJ, that's actually a great idea for both the LAN and the Web client. My brain is still more LAN oriented so I don't know if Ryan has won this debate or not Smiley Happy
by Bronze Super Contributor RyanFarley
on ‎10-29-2009 11:02 AM

RJLedger wrote:
Not everyone will implement an external version control system

Just because they choose not to, why would we want Sage to invest time in building something that we already have? There are so many other things that would be so much better for them to spend their time on.

by Gold Super Contributor RJLedger
on ‎10-29-2009 11:17 AM

There's nothing worse than being in a crunch and trying to get a bundle "assembled" quickly. To do this would be just as Mari posted.. make this process easier and reduce risks of not getting the right (or all) pieces. 

 

It's trivial (for Sage Saleslogix dev)  to add a couple of "tags" to the xml.

by Bronze Super Contributor tagersea
on ‎10-29-2009 12:28 PM
I think being able to go back to a previous version WITHIN the product is very valuable. I dont think it needs to be overly complicated as I agree there are way too many other fixes and enhancements that are needed. However, I wouldnt expect it to be a massive effort to maintain each version of items like the LAN client does.

We have eaten a lot of time because something hiccups in the App Architect and our latest version will no longer build. It would have been very helpful if we could have just selected the previous version and went on our merry way. Note that I am talking about selecting an older version of a quick form for example. I dont want to roll back everything else as the only problem was a single form.
by Bronze Super Contributor RyanFarley
on ‎10-29-2009 02:42 PM

tagersea wrote:
We have eaten a lot of time because something hiccups in the App Architect and our latest version will no longer build. It would have been very helpful if we could have just selected the previous version and went on our merry way. Note that I am talking about selecting an older version of a quick form for example. I dont want to roll back everything else as the only problem was a single form.

I can certainly understand that having it all built in would lower the learning curve. But really, having source control in place gives more benefits than just versioning of files. I can just as quickly as you describe revert back to a previous version of a file in a matter of seconds (and much more). However, I'm not trying to say it wouldn't be useful to have it built in. I just think that using source control with it is the *right* way to do it and building anything into the product like this would likely unneccessarily complicate the flow of using source control (which I woudl still maintain is the *right* way). In this scenario, I woul have to hold on to previous versions of files in my model even though I already have the previous versions in my source control (so I'd have previous versions of previous versions).

 

I guess the way I see it is anything we ask them to build in this area only accomplishes two things: 1) Devote dev time to building something that we already have (and what they would build would not be as complete as what we already have) and 2) Would only complicate using what we already have.

 

I think people who aren't using some sort of SCM with SLX are really missing the boat. Hugely beneficial. 

by Bronze Super Contributor tagersea
‎10-29-2009 03:28 PM - edited ‎10-29-2009 03:34 PM
I am nearly on the same page, Ryan. However, it requires plumbing knowledge to know how to get that quick form out of your source code control. Quite honestly, I think it is a waste of my company's money training someone the underpinnings of the SalesLogix App Architect. We are supposed to be building solutions using the tool, not debugging and reverse engineering the tool.

BTW I never once said Source Code Control was bad. In fact, if Sage was to implement a solution I would hope they would do it on top of an existing source code control system. The value add that they can bring to the table is that when we ask them to "Please go get me version 7.5.2.3 of the Account Detail QuickForm" they would convert that SalesLogix domain speak into "ah we must go get the xxx.xml file from this source code repository along with these cs files, this assembly, etc".

Off my soap box - I know Sage wont do anything about this request anyhow Smiley Happy
Message Edited by tagersea on 10-29-2009 03:34 PM
by Bronze Super Contributor RyanFarley
on ‎10-30-2009 10:50 AM

tagersea wrote:
Off my soap box - I know Sage wont do anything about this request anyhow :smileyhappy:

Haha! I think you are right.

 

BTW, using source control really isn't as hard as you might think. My support teams and even project managers are using it now as well. We don't even use bundles any more to hand off to testing. They just checkout the model from source control, build and deploy. If there's an issue with a form, they just revert back to a previous version to compare. Point is, I don't think it is a time consuming to learn and use as you might think. That said, it usually isn't something that one can just jump into without either taking the time to learn how to use it or having someone show you how.

 

Ryan's List of People to Convert to the Joys of Source Control:

1. Timmus Agersea

 

Smiley Happy

by Gold Super Contributor RJLedger
on ‎10-30-2009 12:01 PM

Let's re-focus back to the subject of the posting - it's about adding VERSION control to AA. It's not about and has nothing to do w/source control. Which - as Ryan has pointed out - we can already do. In fact, kudos to Ryan's open source work in adding "GIT" capabilities to the AA.

 

Dragging Source control into the discussion adds nothing.

We want to hear your cool ideas for enhancing Saleslogix products and services. So add your own ideas or kudo (vote) on the ideas of others here! Watch the most valuable bubble to the top!

I have an idea! How do I get started?

One
Read our submission guidelines.

Two
Search for your idea. If you don't see it, submit a new one!

Three
Provide feedback on the ideas of others by voting with kudos and adding comments.
For more information about using ideas, read this thread.

Four
Track your ideas and those you like. Once you've posted or kudoed and idea, subscribe to be notified via email of the latest updates to the idea. From within the idea, click "Idea Options" which appears above the idea title and choose, "Subscribe to this idea".

Be sure to check back from time to time to see new ideas and status updates!

Here is a quick list of the recent ideas for speedy browsing!
Labels