Yes. The xml is event driven so you can republish at multiple stages through acs configuration. For help on setting these up go look at the admin guide
https://docs.oracle.com/cd/E83928_04/otn/docset.html

Colin,
Go read up on Agile docs for help… for functional questions on usage ask us here to fill in any blanks
https://www.oracle.com/technical-resources/documentation/agile.html

See

https://docs.oracle.com/cd/E83928_04/otn/pdf/administration/html_agaah/output/chapter_29.htm#BABFIBJE

For event management admin guide section on the subject.

Please see

https://docs.oracle.com/cd/E83928_04/otn/pdf/administration/html_agaah/output/appendix_a.htm#CDEECGBH

You may want to create a workflow that allows for this on a limited ability where you have more than one release state.  I am hoping we can say here that this would only happen once per change…..

If this is true you could do something like this

PENDING > SUBMIT > REVIEW > RELEASE1 > SCOPE CHANGE > RELEASE2

This could help you out but I would limit the ability to move to SCOPE CHANGE and RELEASE2 so this does not become an abusive process.  Many times best practices makes processes difficult so that we can become better at our jobs as we hope that a) creators did due diligence to get everything right and b) reviewers did their job correctly.

Best of luck

You two are such jokers… I think if I recall correctly the app that was created was simply just a pointer that took the user to the corporate Agile instance in the mobile device…. there really wasn’t a ‘true’ mobile GUI that was created for customer distribution.

And to answer your question Albert… we are seeing one more update coming up late 2021

https://www.oracle.com/webfolder/community/agile-and-autovue/4319782.html 

but resources would be better placed in looking for the next evolution of the corporate needs for product management.  If you want to respond to your users, let them know that the platform is really no longer a strong plan on the Oracle roadmap and this is the time to learn from your current solution to start discussions on a replacement since these talks can take years to become project reality.

Best of luck.

Wondering why you would want to do this?  There are serious implications involved in this type of activity.  In the event there are events that push xml data downstream this could easily lead to a data imbalance that could be catastrophic.  What I am trying to say unless that business has a really good reason this is never recommended.

The only thing we are going to tell you is to review the associated privileges and criteria…. probably a criteria. Something is different…. just gotta find it.
Best of luck.

Seth,
Once released there is no longer an option to make updates to the item through the ECO. The updates are event related and only trigger at release hence why you are not able to make the updates. What are you attempting to accomplish?

You can give yourself modify privilege access and add the file.  My recommendation would be to add the privilege, make the update and then remove the privilege.  You definitely don’t want to abuse this type of process.