Issue
It was during building the project which has Atomic scope, following popped up.
It is the orchestration designer which is designed to validate the properties against the shapes used. If any of the properties violate or are not as per the validation rule then notification is raised while building the project as "Property value is not valid." It is common for all shapes but to know the exact reason we need to see in the details - it tells what went wrong.
1. Orchestration itself should be set as Long Running.
2. For this click on the white space and set the Transaction Type to Long Running.
In this scenario, it was the usage of Atomic scope in non-transactional orchestration. You can only set a scope to have a transaction type other than None if the orchestration itself is a long-running transaction.
So it is kind of mandatory to mark orchestration as long running if Atomic scope is to be used.
Why it happened:
What to do :
1. Orchestration itself should be set as Long Running.
2. For this click on the white space and set the Transaction Type to Long Running.
In this scenario, it was the usage of Atomic scope in non-transactional orchestration. You can only set a scope to have a transaction type other than None if the orchestration itself is a long-running transaction.
So it is kind of mandatory to mark orchestration as long running if Atomic scope is to be used.
If you have questions or suggestions, feel free to do in comments section below !!!
Do share if you find this helpful .......
Knowledge Sharing is Caring !!!!!!
Thanks for article
ReplyDelete