(legacy) Manage Process properties

(legacy) Manage Process properties

What is it

Each process in Skore has a defined set of properties. Any Administrator or an Editor with Access Rights to a process can edit the processes. It is important to keep these properties up-to-date to help with the ongoing management and searchability of the process.

Process properties

Unique ID

The Unique ID of the process is helpful to create link between processes. Unique ID are shared between processes, files, images.

Name of the process

This is the displayed name of the process that users will see.
Within a process, the current process name is available with the variable {{ process.name }}

Process name vs. diagram title

Within a process, diagrams may have different name
  • Top level diagram has the same name as the process name, but may be renamed
  • Sub levels of processes are automatically named by the upper level activities 

URL / Slug

This is the name of the process that is used to generate the URL of the process. This is automatically generated from the process name, but can be setup manually would you prefer to.
Note that changing the slug may result in broken links if you or anyone has used the URL outside of Skore 

Owner

It is good practice to set an owner for a process.
  • An owner can any user of the workspace 
  • A process may not have an owner
  • If you remove an user from the workspace, it will be removed from process ownership.

Purpose (Description)

Short description of the purpose of the process. May be inserted in a process using variable {{ process.purpose }}

When searching for a process on a workspace, the purpose text is search through too.

Keywords

Keywords help sorting processes.



Next steps

Would you like to export all process properties, switch to the table view on the process to see all data and export.

See also


    • Related Articles

    • (Legacy) Manage access rights of a process

      This is a legacy article. View the latest article here: Process Access Rights Why access rights Not everyone may be allowed to see or edit a process. Access right allow to manage who can do what on a process. Viewers can view To select who can view a ...
    • (Legacy) Manage users in a workspace (With license type, editor, admin and member) (Legacy)

      This article is for the legacy version of Skore. See latest article here: Managing Users Why Manage Users By adding users to your workspace you can control who can see what content. What's more you can start to understand how often processes are ...
    • (Legacy) Manage roles in Skore

      This article is for the legacy version of Skore. See latest article here: Role Manager What is it After defining the work to be done in a process, the next, most important question is who does it? As you create processes in Skore, and add roles, you ...
    • (Legacy) Process versions history

      This article is for the legacy version of Skore. See latest article here: Process Version History.  What is it? When working on a process, new revisions are created so that it is easier to see the history of changes, approve the right revision, or ...
    • (Legacy) Process owner

      What is it In Skore, processes may have a process owner. This is not mandatory but a recommended practice to ensure the right ownership of the processes. How to... How to change the process owner of a process As an editor with "can edit" access right ...