Please enable JavaScript to view this site.

Made in EU
Estate Forums

Navigation: » No topics above this level «

Process Status Transition

In this screen you can register and change transitions between process statuses.Open screen in browser Open Form

A transition specifies a valid change of the status of a process to a different status. This allows workflows to be defined.

Complex transitions can also be enforced with an additional business rule.

Transitions Task Status Screen

The meaning of the entry fields is:

Process Category Old

Reference to the process category in the initial situation as registered in Process Categories.

Process Category New

Reference to the process category in the new situation as registered in Process Categories.

Process Status from

Reference to the process status in the initial situation as registered in Processt Statuses.

Process Status to

Reference to the process status in the new situation as registered in Process Statuses.

Role

Reference to a role as registered in Roles. Indicates which role is necessary to make the process status transition possible.

Involvement Role

Reference to an involvement role as registered in Involvement Roles. Indicates which involvement role is necessary to make the process status transition possible.

Start

Start time of the process status transition.

End

A task process status transition is allowed until this date.

Minimal Limit

Minimum value of the limit of user involvement in relation to this process, project, organization or the involvement of the role (the first of these two which has a value is used), to allow this state transition.

Maximum Limit

Maximum value of the limit of user involvement in relation to this process, project, organization or the involvement of the role (the first of these two which has a value is used), to allow this state transition.

Automatically Try to Set Next Status

Indicates if the system should try automatically to set the next status if the task meets the conditions and there is only one step further possible. The trying stops when there are multiple or zero potential next steps.

PL/SQL Function

Name of the boolean PL/SQL function that results in "true" or "not true". When the function results in ‘true’ the process status transition is permitted. In case the Boolean function results in ‘not true’ or ‘null’ the process status transition is not allowed.

Explanation

Remarks concerning the purpose of the process status transition.

Analyses

Building workflow based on process status transitions is flexible, but sometimes it is difficult determining which steps are run with trying to achieve the next status automatically. With a manual action, several steps at once can be put with any associated actions indirectly through additional business rules. The steps - including automatically made steps - afterwards can be found in the screen Logging.

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer