Introduction
It's common for teams to use the same piece of information in multiple actions. For example, the URL of a Jira project, or a list of known-good domains. If this information is stored directly inside the actions' options and it changes (a new known-good domain is added), every action will need to be updated individually. Resources provide a way to store information in a single, centralized location, so it can then be accessed from any action.
Resources are similar to global variables in software development and can be used in a similar way to text credentials.
Creating a resource
From the list of resources, choose "New Resource". Resources can be plaintext or a JSON object, including an array. There is a 5MB size limit on resources.
Sharing a Resource
Resources will, by default, only be accessible to the Team they are created within. Resources can be configured to be shared with all other teams in the tenant by selecting the 'All teams & drafts' access option. Users can only share with teams for which they have the " resource save" permission.
Need to share with other teams? Reach out to the team to discuss adding the feature to your Tines tenant.
Using a shared resource
Resources with the same name as Resources shared across multiple Teams will use the Resource located within the same Team as the Story.
You can view all resources available to your team by clicking the "Shared with this team" section in the resources page. You will not be able to view or modify the contents of the resource unless you have the relevant permissions in the team owning said resource.
Using a resource in an action
The below action config shows a resource being used in a HTTP Request Action. Data from resources can be used in actions with the RESOURCE key in formulas.
When the above action runs, the resource placeholder will be replaced by the contents stored in the tines_jira_url resource.
Resource locking
Resources can be locked, meaning that they cannot be edited. This ensures that the contents of a resource will remain static, which can be essential for resources that are used by multiple high priority stories. Only team admins and users with permission to manage resources are allowed to lock or unlock resources.
A resource can be locked by clicking the Lock resource button on the top-right of the resource modal.
While locked, it won't be possible to edit any of the resource's contents.
Afterwards, clicking the Unlock to edit button will temporarily unlock the resource. This will allow this user to edit the resource once. The resource will not be unlocked for anyone except the user who clicked the unlock button, and if they exit without editing the resource it will be locked again.
If a user wants to permanently unlock the resource for all users, they can do so by selecting Permanently unlock from the dropdown.
