Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
HI ,
we are planning for the migration from on-premise to appian cloud instance .
In analysis , we came across one question :
currently the each request to appian is identified by process Id(generated by appian) for the status or follow-up. on the request.
Since we are planning to migrate to cloud instance . will there be any case where the process Id can repeat for new request to appian after migration ?
Discussion posts and replies are publicly visible
Process IDs are not guaranteed to be unique for active instances. Not on the old, and not on the new system.
Thanks @stefan for the response ,i need to reframe my question a bit , Once the process is archived, the case became obsolete. So i hope there will not be same two processid active in the old system .
but after migration of the some process instance from the old system to new cloud system . will there be possibility in the triggering the new process
Hope i am able frame the question in better way
This is a very specific question I have no experience with. I suggest to contact Appian.