PF to IPA Conversion

 2 Replies
 1 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
ALB
Veteran Member
Posts: 130
Veteran Member

    I am working on converting Process Flows to IPA.  While trying to cleanup errors, I realized that it would be good to error many types of errors the same.  I realize that there are exceptions.  Has anyone come up with a standard to share?

    Woozy
    Veteran Member
    Posts: 709
    Veteran Member
      Hi AngelaC,

      I started going down the road of building a standard, but I couldn't really find one that I could use for everything, However, I do have some "general rules" based on node types - specifically email, sql, and Landmark - for flows where logging will be minimal. If I will be using full logging (I do this for all our "action" flows) then I just use the default logging values because the logging provides the information I need.

      For "No Logging" flows:
      For email, I typically include the to/cc values, and often the descriptive name associated to them (i.e. the recipient's name, EmpID, or ActorID).
      For SQL, I always include the key fields, and will often just copy/paste the entire query into the error node so I can just grab it from the error message and paste it into a SQL client for review. For Landmark, I typically include the business class, action, and key fields so I can attempt the call manually in designer.

      For the other node types, it just depends what the node is doing and what info is important for troubleshooting.

      Good Luck.
      Kelly Meade
      J. R. Simplot Company
      Boise, ID
      ALB
      Veteran Member
      Posts: 130
      Veteran Member

        Thanks, Woozy!