Cards are created to request available solutions in an organization. To request a solution, users fill out forms in orchestration, capturing the details of the solution. The card is then assigned to individual users, generally to be performed within a defined period.
Say you need to book accommodation for an employee during their head office visit, you can create a card requesting the related solution. Based on the card parameters, a corresponding blueprint in the orchestration will be mapped.
Access privileges: Users with Create Cards permission in the Orchestration will be able to create cards in the corresponding orchestration.
This is the conventional view, where all the cards are listed in chronological order, by default.
Kanban view displays the active cards available in the stages of specific forms.
How to reorder stages in kanban view
By default, the Kanban columns are displayed in alphabetical order of the blueprint stages. However, this order can be interchanged.
- Hover over the stage name in the kanban column.
- Click and drag the column to the desired location.
Reordering stages in the kanban panel does not reorder the stages in the respective blueprint.
View card details
To view all the details of the card:
- Navigate to the Cards tab and select a card that you would like to view the details of.
- The ensuing page will hold all the card details like card name, card creator, associated orchestration, current stage, associated blueprint, fields, comments, and activities.
Card fields
Title
This field holds the card's title. You can modify the title only if you have both the
Edit permission on the card and the
Read/Write permission for Title field.
Learn more about
Card-Level and
Field-Level edit permissions.
Description
A short description about the card can be mentioned here. You can only modify the description if you have both Edit permission on the card and Read/Write permission for Description field.
Team
This field displays the team that can work on the card. The assignee must be a user from this team. The card can be picked up by any user from the team.
Assignee
This field holds the user responsible for executing the card. You will not need Edit permission to modify this field.
- A user can pickup a card:
- When the user has Access Cards permission in the Orchestration and also has the Assign permission under the Cards to me category.
- When the user is an Admin.
- When the user is part of the assigned Team.
- A user can assign a card to other users:
- When the user is an assignee of the card and also has Assign permission under the My Cards to others category.
- When the user has the Assign permission under the Cards to others category.
- When the card is assigned to the user's Team.
Due on
This field holds the card's due date. You can only modify the due date if you have both Edit permission on the card and Read/Write permission for Due on field.
Priority
Priority of the card can be specified here. It helps the assignee prioritize his work diligently. You can only modify the field if you have both Edit permission on the card and Read/Write permission for Priority field.
Attachments
Any file related to the card can be attached here. The size of the attachment must be lesser than 65 MB. You can only modify the field if you have both Edit permission on the card and Read/Write permission for Attachments field.
Attachments can be downloaded or previewed. Attachment preview is supported only for these formats: all image files, pdf, txt, xml, jsp, json, java, html, htm, ppt, pptx, pps, ppsx, docx, doc, rtf, odt, docm, dot, dotm, and dotx.
Actions
You will be able to view and perform actions in the card if you have Access Cards permissions in Orchestration or if mentioned in 'Who can perform this transition?' section in Blueprint.
Other fields
Other custom fields designed in the form can only be edited if you have both the Edit permission on the card as well as the Read/Write permission for the particular field.
Comments provide a space for initiating collaboration on the card. To edit comments, the user should have both the Edit permission on the card as well as the Read/Write permission for the comment field.
Only the user who adds the comment will be able to edit it. Comments can only be deleted by the Admin or the user who added them. However, Admin will not have access to delete the attachments added to comments.
Activities
All actions performed on the card are displayed as Activities . Every user will be able to view all user activities except the ones performed on fields with the Hide permissions.