As far as the problem migrating expressions, rules and constants across environm

hayleyw over 12 years ago

As far as the problem migrating expressions, rules and constants across environments when they are in a doForEach function, has anyone come across either a workaround for this or an easy way to identify which expressions, rules and constants are effected?

Thanks...

Discussion posts and replies are publicly visible

0 Shaun Kilby
Appian Employee
over 12 years ago

One work around would be to export the application and do a text search for 'doForEach'. This way you could identify the inputs for each of the functions. Then make sure to add these inputs to your application.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hayleyw over 12 years ago

That's great. Thank you for that Shaun.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 cody.smith
Appian Employee
over 12 years ago

If you are missing objects upon export, you can use the "Add Contents" feature of the Application Designer to add all objects within top-level Rules and Process Model folders--if you have them organized by application.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 12 years ago

Another way you could track the use of doforeach() is to wrap their use in another rule and use good naming convention. The dependency checker will catch the wrapper rules and it will be easier for you to track down the actual rules within doforeach()
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 12 years ago

This way, you do not have to search through the application export, but only view the rules within the applicaiton builder. If you do decide to go the xml search route, you will only have to search through the "content" folder through much smaller and easier to read files.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel