Publishing checks
When you click Publish, LINA checks the saved template. If anything is missing, publishing stops and the designer lists every problem by name. ‹name› stands for the name of your figure, line or action.
The messages say what to fix. For the figures and fields they mention, see Design a process template.
Start and the start rule
- “‹name›” asks for its due date at start, but the process starts automatically on a page event — nobody is there to enter it. Choose another way.
- The subprocess “‹name›” asks for a due date when the process is started, but this process starts automatically on a page event — nobody is there to enter it.
- Start runs on a page event: choose the event and the space.
- Start runs on a page event: choose the space.
- Start runs on pages created under a parent page: choose the parent page.
- Condition ‹number› of Start has no values.
- A template of this space can start only on pages of this space (‹space›).
- The template needs exactly one Start figure; it has ‹number›.
- Start needs exactly one outgoing line; it has ‹number›.
- Nothing may lead into Start.
- Start must lead to a step, or to an End that waits for something (tick what it waits for).
- A figure has no name (‹figure type›).
- The subprocess “‹name›” has no template chosen.
- The condition “‹name›” waits for nothing; tick what it waits for.
Forks and lines
- The fork “‹name›” branches on the document state, but the template has no states. Add them under Document states.
- The fork “‹name›” has no line for ‹states›; add those lines or mark one line “otherwise”.
- The fork “‹name›” has no evaluable condition yet.
- The line “‹line›” has an end that does not exist.
- The line “‹line›” from the manual fork needs a label.
- Two lines from the fork “‹fork›” are for the state “‹state›”.
- The line “‹line›” leaves an end figure.
Actions
- The e-mail action “‹name›” has no text.
- The ticket action “‹name›” is missing: ‹fields›.
Due dates and reminders
- “‹name›” waits for a due date: choose the date.
- “‹name›” waits for a due date: enter the number of days.
- “‹name›” waits for a due date: name at least one person to ask for it.
- “‹name›” waits for a due date: choose where the date comes from.
- “‹name›” sends a reminder before its due date: name at least one person to remind.
Document states
- Document state ‹number› has no name.
- Two document states are called “‹name›”.
- The document state “‹name›” has no group (in progress / valid / not valid).
- The action “‹name›”: choose the document state.
- The end “‹name›”: choose the document state.
- The subprocess “‹name›”: choose the document state.
- The line “‹name›” from the fork: choose the document state.
- The action “‹name›”: the chosen document state is no longer in the template’s list.
- The end “‹name›”: the chosen document state is no longer in the template’s list.
- The subprocess “‹name›”: the chosen document state is no longer in the template’s list.
- The line “‹name›” from the fork: the chosen document state is no longer in the template’s list.
Service account and deleting
- The service account of this template is not on the list of allowed service accounts (app Configuration). Choose another one, or ask a Confluence admin to add it.
- Used as a subprocess by “‹name›”.
Older templates
- Moving a page no longer starts a process; choose “Page created” or “Page created under a parent page”.
- “‹name›” is a Step, which no longer exists. Replace it with a Condition (waits for tickets, a date or a person) and a manual fork (a person chooses the way on).
- The fork “‹name›” branches on a Step’s result; Steps no longer exist. Use a manual fork, where a person chooses the way on.
Publishing also checks Jira: that the account creating tickets — and you — may create issues in the chosen project, that the issue type exists, and that the mandatory fields of its create screen are filled. Those messages name the project and field.