This is the toolbar configuration console for this business class: Note how none of the actions that we can see in the toolbar in the first screen shot are actually set in the “Actions Pinned to Toolbar” in this screenshot. So how do we modify a “default” action and why do I mean by “default” action anyway?Simply put, a “default” action is an action defined at the Business Class level and then not overridden anywhere else (such as the list).It is very non-obvious how to modify these actions with Configuration Console.
We can accomplish this by copying the LPL from the Business Class (or wherever the inheritance is from) and applying the modifications we want. In this example, I will inquire on GL10.1 with cache set to true and then update the Company name field.
For this example, the fact that the “Actions” declarative is not present in the list LPL means that it is defaulting. For those who are just joining us (and didn’t read part 1), by turning on caching, I can update just the company name field in the update node instead of having to pass in all of the fields again. I hate surprises to the point that I actually don’t care if I know what happens in a movie before I see it.
I can’t explain this currently, but it would seem that there are certain actions that are inherent to Landmark itself and all Business Classes inherent them. After some questions and reviewing the post, I realize that I didn’t fully explain how to use it within the context of Process Automation or Process Integrator. Since we’re on Process Automation, my example will be from PA.
Regardless of where they are defined, it demonstrates the Java concept of inheritance: unless overridden, a child object – in this case a list – have all the same properties of their parent unless otherwise specified. The only difference between Process Automation and Processflow Integrator is that PA will return the XML from the Lawson Transaction Node (AGS).
I dislike both of those options because they both involve the word “manual”. All of the information about the flow is in the XML, so you can effectively read ahead to what the flow will do next and thus predict the future.