I have 2 issues :
¤ Why do I have "Create", "Cancel" or a "Apply" buttons that appear while I didn't declare them in the transitions ? Is a cmdbAbstractObject (parent class) has an internal lifecycle ?
¤ Why do I have to confirm each transition in another page ? It means that I have to click 2 times for each action...
Any information would be the welcome :)
Regards,
Rafael.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You have those buttons on all objects regardless it has or not a lifecycle with or without transition defined:
Cancel / Create on creation form
Cancel / Apply on modification form
If it has transitions defined then each transition will be proposed on top of those standard actions.
The Create/Apply can be hidden (with a parameter) on the Portal if Transitions are available for the user, but this lead to wierd behavior sometimes, as the Object cannot be created in state New...
Last edit: Vincent @ Combodo 2018-08-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for this additional explanation. It makes sense. But is there a way to use these buttons in my own lifecycle ? I mean I would like to trap the user actions on it to manage my own transitions.
About my second comment : is it possible to use the lifecycle without having the confirmation page after each click ?
Thanks again for your help !
Regards,
Rafael.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You cannot use those buttons in your own lifecycle, as Cancel correspond to "no action at all" and Create/Modify correspond to stay on New/current state with no transition applied.
You may make the Apply button useless by setting all fields in read-only mode on that state, but it still will be available.
There is currently no way to bypass the transition confirmation page, even if that page contain no proposed field, but in general a transition is made for requesting particular data, which can only be set during that transition, so that the reason why those form exists, you don't need to do modify then the transition, you can apply the transition with the action menu from the details screen.
Having a parameter to auto-confirm transitions without requested fields, is a possible enhancement. Should it be global on all transitions of all objects, should it be a Datamodel parameter defined on each transition of each class, or a combination of both a global default and an explicit parameter per transition... We will see, but I can't say when we will have it.
Last edit: Vincent @ Combodo 2018-08-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you Vincent.
I understand. I always try to began in following the logic of the software I use. So I want to add action buttons, I first try with the lifecycle.
For my part, if no specific parameter have been declared in a Transition, it would be a good idea that the confirmation page will be bypassed.
In this case le lifecycle doesn't help me. Is there another way to manage a workflow other than the lifecycle ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all !
I have created a new type of object with its own lifecycle
https://ibb.co/kEO6A9
I have 2 issues :
¤ Why do I have "Create", "Cancel" or a "Apply" buttons that appear while I didn't declare them in the transitions ? Is a cmdbAbstractObject (parent class) has an internal lifecycle ?
¤ Why do I have to confirm each transition in another page ? It means that I have to click 2 times for each action...
Any information would be the welcome :)
Regards,
Rafael.
You have those buttons on all objects regardless it has or not a lifecycle with or without transition defined:
If it has transitions defined then each transition will be proposed on top of those standard actions.
The Create/Apply can be hidden (with a parameter) on the Portal if Transitions are available for the user, but this lead to wierd behavior sometimes, as the Object cannot be created in state New...
Last edit: Vincent @ Combodo 2018-08-30
Hi Vincent !
Thank you for this additional explanation. It makes sense. But is there a way to use these buttons in my own lifecycle ? I mean I would like to trap the user actions on it to manage my own transitions.
About my second comment : is it possible to use the lifecycle without having the confirmation page after each click ?
Thanks again for your help !
Regards,
Rafael.
You cannot use those buttons in your own lifecycle, as Cancel correspond to "no action at all" and Create/Modify correspond to stay on New/current state with no transition applied.
You may make the Apply button useless by setting all fields in read-only mode on that state, but it still will be available.
There is currently no way to bypass the transition confirmation page, even if that page contain no proposed field, but in general a transition is made for requesting particular data, which can only be set during that transition, so that the reason why those form exists, you don't need to do modify then the transition, you can apply the transition with the action menu from the details screen.
Having a parameter to auto-confirm transitions without requested fields, is a possible enhancement. Should it be global on all transitions of all objects, should it be a Datamodel parameter defined on each transition of each class, or a combination of both a global default and an explicit parameter per transition... We will see, but I can't say when we will have it.
Last edit: Vincent @ Combodo 2018-08-30
Thank you Vincent.
I understand. I always try to began in following the logic of the software I use. So I want to add action buttons, I first try with the lifecycle.
For my part, if no specific parameter have been declared in a Transition, it would be a good idea that the confirmation page will be bypassed.
In this case le lifecycle doesn't help me. Is there another way to manage a workflow other than the lifecycle ?