{"id":2718,"date":"2017-10-13T09:15:06","date_gmt":"2017-10-13T08:15:06","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=2718"},"modified":"2017-10-16T14:57:00","modified_gmt":"2017-10-16T13:57:00","slug":"parametrics-document-publisher","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/parametrics-document-publisher\/","title":{"rendered":"Parametrics in Document Publisher"},"content":{"rendered":"

Parametrics <\/strong><\/em>can be very useful in Document Publisher<\/em>. It uses a question mark ?<\/strong> as a marker to Document Publisher<\/em> that this is an option and needs to be filled\/selected by the user.<\/p>\n

It can allow users to set the Identity\/key of a single item or more to be output. This can be used in a hierarchy or with a single item type. Parametrics<\/em> can also be used to set different properties and options in filters.<\/p>\n

Single Parametrics<\/h2>\n

Using a single Parametric (?)<\/em> allows a user to publish a template many times but use a different item Identity<\/em> or Key<\/em> each time. Note:<\/strong> Using a single parametric in several places in the template will always use the same item identity or key each time.<\/p>\n

A parametric<\/em> can be used at the database\/top level or at the field level to set the items to be published. At the top level the parametric<\/em> is entered for the Identity<\/em> or Key.<\/em><\/p>\n

\"Single
Single Parametric set at Database level<\/figcaption><\/figure>\n
\"Specify
A popup for a user to set the Key(s) at a database level item.<\/figcaption><\/figure>\n

They can also be used in a filter for field to set or restrict the items to be output.<\/p>\n

\"Using
Using a category to detemine if a field tag is output.<\/figcaption><\/figure>\n

In this case the Requirement<\/em> attribute of Identity<\/em> will only be output if its Item Status<\/em> is set to Accepted<\/samp>.<\/p>\n

\"This
This allows the user to set the Item Status Option.<\/figcaption><\/figure>\n

As you can see below, only items with a status of Accepted <\/samp>have both the Identity<\/em> and Key<\/em> output for the Requirements<\/em>.<\/p>\n

\"Small
Small excerpt of the items output<\/figcaption><\/figure>\n

Named Parametrics<\/h2>\n

Using a Named Parametric<\/em> (?named)<\/strong> means a user can have several different parametrics<\/em> throughout the template and each can be set at time of publishing. So for example the user can set one named parametric<\/em> for output based on one option of category<\/em> (e.g. Agreed<\/samp>) and then later in the template use a different named parametric to output based on a different category option (e.g. Rejected<\/samp>).<\/p>\n

\"Named
Named Parameters for 2 different Paragraph Group Tags<\/figcaption><\/figure>\n

During publishing a popup will allow the user to select Agreed<\/em> for the first Paragraph Group<\/em> popup:<\/p>\n

\"Named
Named Parametric for Status 1<\/figcaption><\/figure>\n

They then can select Rejected<\/em> for the second Paragraph Group<\/em> popup:<\/p>\n

\"The
The second popup to select a different Status<\/figcaption><\/figure>\n

The published output will then show the 2 different outputs in the same document.<\/p>\n

\"Output
Output using the above options<\/figcaption><\/figure>\n

These named parameters can even be used in several places within the template. The user may want to show the Agreed<\/samp> Requirements<\/em> and System Requirements<\/em> in one document. As both item types use the same category<\/em> (Item Status<\/em> in our Demo) then the same named parametric<\/em> can be used for both item types.<\/p>\n

\"Using
Using Named parametrics for both Requirements and System Requirements<\/figcaption><\/figure>\n
\"Output
Output using the same Named Parameters twice<\/figcaption><\/figure>\n

In the above screenshot, the 2 named Parametrics<\/em> have been used for Requirements<\/em> and System Requirements<\/em> and the output shows all the Agreed<\/samp> items but that there are no Rejected<\/samp> System Requirements<\/em>.<\/p>\n