Understanding of Processes

Ewanm

I am developing an application which required to change the status of a record through various staged during its lifecycle as shown below.

Parked -> Raised -> Allocated -> Complete -> Closed

during this workflow, before progressing to the next status, various other attributes require to be in certain conditions before it is allowed to progress to the next status.

I am trying to use 'REPORT ERROR' in a process to check this.

I have a save button on the'Allocate' form and the Process is set to run after saving.

If Tickets.Status='Raised' AND Tickets.AssignedEngineer IS UNDEFINED Then
REPORT ERROR 'Please select Engineer to proceed'

If I insert the check rule above in the BO update rules, it appears to work ok but when inserted in a Process, it does not appear to execute.

On reading the User Manual, it would appear it should run and if no Failure Rule is set, it should work exactly as in the BO update rule.

Is this correct or am I misunderstanding?

Thanks

BLOMASKY

I am a little confused. When are you calling this process?

Do you have a rule in the BO that says something like:

IF Ticket.Status WAS CHANGED THEN CallYourBO

Also, if you do, I assume your process has the Ticket BO as an input.

Correct?

Bruce

Ewanm

Thanks for the reply,

The process is called by AwareIm automatically when the form save button is pressed and the save function is complete. There is a selection in the 'Panel Operations' to Execute process after save. This is ticked and the process name is selected in the drop down box.

I do not have a rule to call the process.

Yes the Ticket BO is defined as the process input.

PointsWell

If you are calling the process after the Save has completed then you are not going to get the effect of your error check on the record.

You would be better to place this into the BO rules with a condition as Bruce mentioned

If BO.attribute WAS CHANGED THEN ProcessName

What does the logger show as happening when you run the process?

I am guessing that there are a whole set of requirements based on attribute settings in order to proceed to the next step which lends itself nicely to WAS CHANGED TO in the Update Rules for the BO

IF BO.Status WAS CHANGED TO 'Raised' AND BO.Engineer IS UNDEFINED THEN REPORT ERROR 'Message' ELSE DoSomething

Which would have the effect of interrupting and preventing the save until either the Status was reverted to a lower level or an Engineer is defined.

I tend to use the after save run process functionality to do things that are not necessarily related to the BO, for example, after save view another BO or change VP, and keep all the attribute conditional elements to the Update Rules (with conditions applied to them and set to not when referenced to keep things leaner) as these always are triggered when the BO is being saved.

Of course I could have completely misunderstood what you are trying to achieve.

Rennur

I am trying to use 'REPORT ERROR' in a process to check this.

In a process, when the rule containing REPORT ERROR is executed, it cancels the entire process.

Option:
In your after-save process replace REPORT ERROR with a DISPLAY MESSAGE and EDIT functions.
(you can also utilise the DISPLAY QUESTION and Question.Reply="Yes" or <>"Yes" in a two rule combination)

E.g. of DISPLAY MESSAGE
RULE 1:
If Tickets.Status='Raised' AND Tickets.AssignedEngineer IS UNDEFINED Then
DISPLAY MESSAGE 'Engineer missing. Select engineer to continue'
EDIT Tickets USING "MyEntryFormName (e.g. Allocate)"

RULE 2:
If If Tickets.Status='Raised' AND Tickets.AssignedEngineer IS UNDEFINED Then
ProcessName (re runs the process until engineer is selected)