Hello Appian Engineering,
Like to suggest :
Scenario :
When a developer working on any object rules ,
It could be UI or expression or model
Appian always had version from past 12plus years
Which is good
As we progress it will be good to have save and commit
1. Save basically a developer works whole day in dev and keep saving not to lose his work but that does not mean it’s working and ready for others to use
2. Commit when developer decides it’s ready for checkin and can be used in site other he needs to commit and mandatory to write comments
May be a ticket that developer is working against or an enhancement for targeting a particular release
Many times we see 100s of versions but more than 75% are just saves of a line change and dev testing how it looks etc and after ten saves developer decides good for real change and closes that piece of work
Just compare how eclipse or vscode git integration works
Even further shelving concept from Microsoft
Having been 12yrs with appian tech
I feel this will be great feature
As of 2022.3 I have not seen
The designer landing page is awesome though
Rayudu A
Discussion posts and replies are publicly visible
Actually, that is a great idea but there are some arguments to it.
This seems a work around
Disagree with ur idea.
As developer working half way without save it times out or take break browser close all work lost
Especially you know those related records guids when saved local file will look like :)
One has to copy whole and keep in local notepad or so etc
It’s not the right way
Unknown said:Actually, that is a great idea
There is no need to disagree. I said it's a great idea but I was putting those arguments considering how Appian works. But if they implement it, that would be a game changer.