Community
Thumb_2

Intelizign - LiveDoc Save

 This plugin triggers a custom script on the Pre- and Post-Save actions of a LiveDoc document for Validations/Actions.

Description

This plugin gives you the ability to perform different actions/validations before saving a LiveDoc document, as well as trigger multiple actions after the save. This all is possible using a smarty build script engine that executes user-written custom scripts. 

 

Product Features

  • This extension makes it easy to run your own script files before or after saving/creating a LiveDoc document.
  • It gives you the option to perform an action before a LiveDoc is saved (pre-hook with the option to deny the save) or after it has been successfully saved.
  • It does not require a Polarion server restart to deploy/adjust scripts.
  • It is easy to plug into any Polarion instance.
  • An easy guide and sample script are provided for better understanding.

 

Installation

  1. Stop the Polarion server.
  2. Create folder path \Polarion\polarion\extensions\com.intelizign.livedocsave.actions\eclipse\plugins
  3. Copy the extension file com.intelizign.livedocsave.actions_X.X.X.jar to folder \Polarion\polarion\extensions\com.intelizign.livedocsave.actions\eclipse\plugins.
  4. Create folder path \Polarion\scripts\livedocumentsave - this is the place where you will be placing your custom scripts.
  5. Delete the .metadata and .config folders in the workspace directory, usually located at C:\Polarion\data\workspace.
  6. Start the Polarion server.

 

Getting Started with Sample Example

  1. After the installation is finished, you can now easily set up your scripts.
  2. To do so, copy the file \examples\documenttitle-prefix\pre-save.js from the directory contained within this extension to the \Polarion\scripts\livedocumentsave folder. Now, every LiveDoc document will automatically have your User ID appended as a prefix to the Title when you save/create it.

 

Custom Script Naming Convention

  • As the script engine will pick up a custom script only when the naming convention is followed properly, please follow the below syntax for naming a custom script file:
    {{project-id}}-{{document-type-name}}-{{action pre-save/post-save}}.js
  • If project-id is not provided, the script will trigger for all projects with the given document-type-name.
    {{document-type-name}}-{{action pre-save/post-save}}.js
  • If project-id and document-type-name are not provided, the script will trigger for all projects and all document types.
    {{action pre-save/post-save}}.js

 

What's New in Version 1.2.0

Updated June 2023

Version 1.2.0
- Added Support for Polarion 2304 - Java 17
- Examples updated to work with GraalVM JS Scripting Engine

Version 1.0.0
- Initial Plugin Release

 

Information

Vendor Intelizign Engineering Services GmbH
Published Version 1.2.0 - June 2023
Categories
Price Free
159 Downloads
Community Supported Extension This extension is not supported by Siemens PLM.
Requirements The extension was developed for and tested with:
Version 1.0.0
* Polarion 20 R1 (3.20.1)
* Polarion 21 R2 (3.21.2)
Version 1.2.0
* Polarion 22 R2 (3.22.2)
* Polarion 2304 (3.23.4)

Related Extensions