This content has been marked as final. Show 4 replies
we handled similar situation through personalization as follows:
1a. Write the validation condition in personalization on WHEN-NEW-RECORD-INSTANCE of ORDER Block.
Through actions, display error message and disable Book button.
1b. Write the negative of validation condition in personalization on WHEN-NEW-RECORD-INSTANCE of ORDER Block.
Through actions, enable Book button.
2. Disable Book order button in LINES Block
3. Train the users to enter the order header first, order line next and then come back to header and click book (if allowed).
We do want to let the Book button can always be enabled.
And we want to accomplish the work flow as follows:
input data(user)-save order(user) - try to book order(user) - check(system) - popup message & hold order(system) - confirm(user,offline) - release hold(user) - repair illegal data(user) - try to book order again(user) - check again(system) -...
the text which be bolded is the things that we need to handle.
You restrict order booking based on conditions by using
Trigger Event: OM_PRE_BOOK_EVENT
Condition: As required
Processing Mode: Both
Message: Error: Order Can't be booked
Builtin : RAISE FORM_TRIGGER_FAILURE
We also have found the cutomer trigger that can be used.
Big thanks & Best wishes.