Using the Glossary in Skore

Using the Glossary in Skore

Who can create and edit terms: Editors and above
Who can view terms: Anyone

Introduction

O2C? P2P? RFP? ISO? LOL? BR? HR? ER? What do these mean and how am I meant to keep track?

Why use the Glossary?

Acronyms and abbreviations are not always understood by everyone and can make your processes confusing and create barriers in engaging the organisation.
You can document these as part of your process library and these terms can be used directly in your processes thanks to our dynamic Glossary!

How to add a Glossary term from the workspace



How to add a Glossary term from within a process


    • Related Articles

    • Using Attachments in Skore

      Why attachments Attachments are helpful to add commentaries, context, details to an activity Types of attachments Text : ideal to capture free-form information such as detailed  URL Custom field External Content Attachment normally open in the right ...

    • Decision boxes / diamonds in Skore

      Introduction Users that are new to Skore may ask how they draw, or represent, a decision diamond commonly found in other types of process mapping. Skore is based on the Universal Process Notation (UPN) which doesn’t use decision diamonds but does ...

    • Quantify a Process in Skore

      Why cost a process Understanding the cost of a process helps you make decisions about what and how to change it. For example, if you are looking at automating a part of a process you can use this feature to understand the opportunity cost saving that ...

    • Connect to Skore API via Postman

      Public API Documentation https://documenter.getpostman.com/view/9179336/SzS7Nk63#74566d1c-a415-46be-b991-da41f8a40569 Import collection in Postman (and keep in sync) · In postman desktop client, click “Import” · Paste the following URL ...

    • How to setup Two Factor Authentication in Skore

      What is 2 Factor Authentication (2FA) ?  "2FA" is a way to secure an account by making sure the user trying to login really is the user. This is done by asking a second security question that is generated from another source.  At Skore, we do it ...