BLOMASKY wrote:Silly me. I thought it would always run after a record is created / saved. I have an entry screen, called from a process and after the record is saved, I have some conditional logic that I want to call based on fields in the new record.
Wonder if I could get more info re: when it is (and isn't) called.
I didn't really understand the logic of it personally.
If there is conditional logic based on the field values would a business rule on the BO not be a better route to follow?
IF BO IS NEW AND BO.Value=1223 THEN call a process
If the randomness of the order of business rule execution is an issue I have worked out a way to control that using other status fields.
for example, I have an ISBN checker that when the user enters an ISBN I want to check that the ISBN is valid, and if it is ISBN10 then create another ISBN13 record and then once that is all complete go collect some data via a REST API.
I control the order of all this by having a validity attribute
so first step checks the ISBN is valid
IF BO IS NEW AND BO.ISBN WAS CHANGED AND BO.ISBN IS DEFINED THEN check isbn (which sets valid flag)
IF BO.hValid WAS CHANGED TO 'Yes' THEN count length of ISBN and set an attribute
IF BO.Length WAS CHANGED TO 10 THEN do the next step.
Obviously you could manage this all via one field.
IF BO IS NEW AND BO.Stage='New' THEN do the first bit of checking and set status to Stage1
IF BO.Stage WAS CHANGED AND BO.Stage='Stage1' THEN do the next bit of processing set to Stage 2
If your processing is complex then call a process to off load the more complex work with the last step being to change the Stage value.