Explanation about best practices.

Hi saic929,

As all best practices refer, they try to help you to create the best end user experience and governate systems properly, so this scripts are a guidance that you can use or not, but are recommended.

• From my point of view, it is recommended to not customize a lot any component or interface, because it is better to think that everything could be reusable, and not very specific to a concret purpose.
• It is better to control all the options, and avoid users to set wrong information, that's why is better to limit the options, it is not related with offer less options that they need, but control or avoid possible mistakes. e.g. set a T/F component like a radio button or check box when you ask a yes/no question to the user, better than set a text field.
• When you use processes, you have traceability, you can review the history of data and more functionality than maybe use a plug in or a function, so it depends on the case, but if it is a critical process or action it is recommended to use processes. e.g. write to a data store.
• When hidding variables, they are not appearing in reports, nor available for mapping to parent processes when the process model is used in a Sub-Process Activity.
  • You can not make a variable hidden if it is a parameter.
  • Changes to hidden variables do not appear in the process history.
  • To expose the process variable within newly started process instances, clear the Hidden checkbox.

Hope it helps you.

Hi saic929,

As all best practices refer, they try to help you to create the best end user experience and governate systems properly, so this scripts are a guidance that you can use or not, but are recommended.

• From my point of view, it is recommended to not customize a lot any component or interface, because it is better to think that everything could be reusable, and not very specific to a concret purpose.
• It is better to control all the options, and avoid users to set wrong information, that's why is better to limit the options, it is not related with offer less options that they need, but control or avoid possible mistakes. e.g. set a T/F component like a radio button or check box when you ask a yes/no question to the user, better than set a text field.
• When you use processes, you have traceability, you can review the history of data and more functionality than maybe use a plug in or a function, so it depends on the case, but if it is a critical process or action it is recommended to use processes. e.g. write to a data store.
• When hidding variables, they are not appearing in reports, nor available for mapping to parent processes when the process model is used in a Sub-Process Activity.
  • You can not make a variable hidden if it is a parameter.
  • Changes to hidden variables do not appear in the process history.
  • To expose the process variable within newly started process instances, clear the Hidden checkbox.

Hope it helps you.