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

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

Mike Cichy — Tue, 26 Jun 2012 20:19:08 GMT

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.

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

Mike Cichy — Tue, 26 Jun 2012 20:17:22 GMT

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()

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

cody.smith — Tue, 26 Jun 2012 19:23:38 GMT

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.

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

hayleyw — Tue, 26 Jun 2012 18:17:52 GMT

That's great. Thank you for that Shaun.

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

Shaun Kilby — Tue, 26 Jun 2012 18:10:57 GMT

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.