Contents x
    My Resources
      • Print
      • PDF
      Contents

      My Resources

        • Print
        • PDF
        Article summary

        My Resources lists all the resources the user is allowed to checkout. Each resource has a specific action/permission configured to a profile allowing a user to checkout. 

        1. Login to Britive.
        2. Click on My Resources from the navigation menu to view the resources. 
        3. Select resource labels from the drop-down list for grouping the resources by resource labels. After selecting the resource label, groups are created for each available label value.
        4. The following details of each resource are shown here:
          • Resource Name
          • Resource Labels
          • Profile Name
          • Access: If the profile is checked out, this column shows the time remaining for a checked-out profile.
          • Status: The latest approval status is shown here.  
            • Checked Out: The profile is checked out.
            • Approval Required: Approval is required to check out a profile. 
            • Pending Approval: The approval request is pending.
            • Available: The user can check out a profile. [Note: In case of a profile that requires approval, the remaining approval validity duration is also displayed in this column]
          • Action: Check out, Check in, or Request (for profiles requiring approvals).
        5. If the required profile needs an approval:
          1. Click on the Request button.
          2. Enter justification and click Send Request. The user is notified when the approver approves the request via the specified notification medium defined in the policy. The request can be tracked under the My Requests page.
          3. For the Advanced Settings enabled profile approval flow, see Checkout Advanced Settings enabled profiles.
        6. Click on the Check Out button to check out the profile.
          1. If the profile policy is configured for MFA verification, enter the OTP from the Authenticator app and click Proceed to Checkout. If the user has not registered a verification device, see User Settings to register a device.
          2.  For profiles where advanced settings are enabled, see Checkout Advanced Settings-enabled profiles.
          3. The status changes to Check Out Submitted and then to Checked Out. It also displays the validity of this check-out.
          4. Clicking on the Console button under the Access column opens the Access Credentials window. This displays a response from the broker. The Original Credentials tab displays the entire checkout details and the subsequent response templates associated are displayed in other tabs.
        7. Click on the Check In button to manually check in the checked-out profile otherwise, the profile is automatically checked in after the expiration time specified in the profile.

        All the listed profiles can be filtered as follows:

        • Favorite: All profiles marked as Favorite are filtered and listed here. The user can add a particular profile to a favorite collection by clicking Mark as favorite icon next to the profile name.
        • Frequently Used: All frequently used profiles are listed here.

        Checkout Advanced Settings-enabled Profiles

        As per the effective advanced settings applicable for the application profiles/resource profiles, the system prompts the user to provide the justification and ITSM ticket number for submitting the checkout/approval request. Some key points to take note of :

        • Justification is required for check-out if the Advanced Settings -> Justification Settings -> Justification Required at Checkout is enabled.
        • If the regular expression is defined in the Advanced Settings, the user must provide the justification matching it. Otherwise, any value is accepted.
        • It is mandatory to provide the ticket number for check-out and approval requests if ITSM is enabled in the advanced settings.
        • If more than one ticket categories are configured, the requester needs to select a category during checkout/approval operation, and then provide the ticket number.
        • The requester can provide the exact ticket number and view the details if the ticket is valid. The ticket number provided by the requester is validated against the filter criteria defined in the settings. 
        • Alternatively, the requester can search for tickets and select one from the search results. The search result only contains the tickets that match the filter criteria defined in the settings. 
        • For ServiceNow incidents/change requests, the searchText is searched in the number and short description fields.
        • For Jira tickets, if searchText is in the Jira issue format then the system searches for the exact matching issue key. Otherwise, the text is searched in the summary and description fields.
        • The provided ticket number is audited with the checkout and approval requests. In the case of approval requests, the ticket number is shared with the approver for approval decision.


        Was this article helpful?
        What's Next

        © 2024 Britive Inc. All Rights Reserved.