Introduction
Understand what a Change Request is in Lunr, how the standard and full Change Request experiences differ, and which one your organisation has given you.
Overview
A Change Request gathers a set of drawing changes under one request so they can be reviewed and released together. Working a request means gathering the documents the change produces, moving the request through its workflow as each stage is reviewed, and releasing those documents once the request is authorised.
Change Requests are listed on a project's Change Requests tab, described in Working in a Project.
The Two Change Request Experiences
Lunr ships two Change Request experiences, and your organisation decides which one you get.
- Standard Change Requests are the original experience. You raise one from a short dialog, then work it on a page with Documents, Comments, and History tabs.
- Full Change Requests are the newer experience. The dialog becomes a full creation page, and the request gains an Overview tab, a Reference Documents tab, and a workflow progress nav.
Which one applies can differ between document repositories, so two repositories you work in may not behave the same way. A Change Request always uses the experience that applies to its own repository, even when you open it from somewhere else.
What Differs
| Standard | Full | |
|---|---|---|
| Raising a request | A dialog asking for a subject and an optional message | A full page also capturing attachments, tags, priority, due date, and reference documents |
| Tabs on a request | Documents, Comments, and History, opening on Documents | Adds Overview, which it opens on instead, and Reference Documents |
| Workflow progress nav | Not shown | Shown across the top of the request |
| The request's message | In the Action Pane, with an Edit action | On the Overview tab |
| Reference documents | Unavailable | Available, with allocation and bulk allocation |
What Is the Same
Both experiences are complete ways to run a change. Whichever you have, a Change Request carries the same workflow and statuses, the same assignee and reviewers, and the same Release All, Download Package, and Generate CR Summary actions. Comments, favourites, Change Request folders, and the search and filters on the Change Requests tab work the same way in both, and Checklist appears in both where checklists are enabled.
No data is converted between the two, so an existing Change Request simply opens in whichever experience currently applies to its repository.
Which One Do I Have?
Select New Change Request in a project's Action Pane and watch what opens.
- A small dialog asking only for a subject and a message means you have the standard experience.
- A full page with tabs, tags, and attachments means you have the full Change Request page.
The request itself tells you too: a Reference Documents tab is only ever present on a full Change Request.
Working in a Project
Open a project and work in it, covering the tabs it offers, the Action Pane, project folders, and subscribing to a project.
Standard Change Requests
Raise a standard Change Request from the Create Change Request dialog, gather the documents it covers, and work it through review to release, using its Documents, Comments, and History tabs.