Skip to main content

FieldLogs

Creating a Custom Lifecycle

In addition to the standard static Lifecycle for content approval, FieldLogs also allows you to design a dynamic Custom Lifecycle to edit, review, publish, and test Templates. Custom Lifecycles are also used to build Resolution Flows for Incidents.

With Custom Lifecycles, you can incorporate complex business rules. Various user forms can be added to different stages of the Custom Lifecycle. The sequence flow in the Custom Lifecycle can be then based on the user input in these forms.

A BPMN (Business Process Modeling Notation) Editor is used to model and customize the workflow required for a Custom Lifecycle.

Steps to Create a Custom Lifecycle

To add a Custom Lifecycle:

  1. From the main menu, go to Enterprise > Organization.

    lifecycle_navigation.png

    The Enterprise Hierarchy is displayed.

    CLC-EHDisplayed.png

  2. Click Lifecycles.

    CLC-ClickLC.png

  3. Against the Template DB to which the new Custom Lifecycle is to be added click Add and select Add Custom Lifecycle as shown below.

    CLC-AddLC1.png

  4. Enter the name of the new Custom Lifecycle and click Create.

    CLC-newCreate.png

    A blank canvas to create your Custom Lifecycle appears.

    blank_canva.png

    Note

    FieldLogs uses a visual modeling language, Business Process Modeling Notation (BPMN) to specify the process workflow of the Custom Lifecycle.

  5. Select a Custom Lifecycle type from the dropdown.

    dropdown.png

    The following options are listed in the dropdown:

    • Template: If you select Template, the Custom Lifecycle created is available for Template Publication.

    • Incident: If you select Incident, the Custom Lifecycle created is available as the Resolution Flow of an Incident.

    • Approval: If you select Approval, the Custom Lifecycle created is available for Document Creation, Update, and Deletion Approval.

    • OP Plan: If you select OP Plan, the Custom Lifecycle created is available for the execution of Operation Plan Tasks.

    • Tryout: It is designed to manage, execute, and monitor the testing process of new or revised Task Card. It ensures a controlled environment where workflows are validated before full-scale implementation, with feedback loops for continuous improvement.

    Note

    By default the Template option is selected.

  6. Drag the required elements from the UI panel to build a Custom Lifecycle.

    UI_panel_options.png

    You can also upload Custom Lifecycles using the upload_button.png button, with BPML as the supported format.

    upload_lifecycle.png

  7. Click save_button_.png to save the Lifecycle.

    save_lifecycle.png

  8. Click publish_icon.png to publish the Lifecycle. A Lifecycle can only be used after it is published.

    publish_lifecycle.png

    You have successfully created and published a Custom Lifecycle which can be used in the content approval process.

    Note that the Battery Check Custom Lifecycle appears in the list of Lifecycles when submitting a Template to the Enterprise for Publication.

    CustomLifecycle-AvlOnTemplate.png

    If the created Custom Lifecycle is of type Incident, then it is available as a Resolution Flow for Incident Definition.

Note

There is a Guideline Validation feature, that checks the Custom Lifecycle dynamically as it is built and offers suggestions and highlights errors.

In this section: