Build

Once you have an understanding of the roles, flows, groups, data and forms, you can start assembling the solution.

You can start building your solution in the library area of an installed PMX instance. Alternatively, if you are creating a solution that needs to be packaged, you might want to start with product structure.

Build order

There are no rules about the best way to do this. However, it is probably woth creating the group structure first, using group profiles and the new group recipe. This will then give you a structure into which you can place other components.

You can then tackle flows one-at-a-time, perhaps in a priority sequence that looks at core processes first and more peripheral ones later. If you can, use or base your flows on the standard ones. If you are writing new flows from scratch, check the "happy path" through the process first to make sure that hangs together, then work through all the other paths.

Packaging

If you want your solution to be installed by others (even if you just want to be able to install it in test and live), then you will need to package it as a product. General packaging standards are described in Metrici development guide, in the Product structure and packaging standards section.

The easiest way of getting an appropriate product definition folder is it to base it on the PMX product definition structure. Speak to Metrici support who should be able to provide you with an up-to-date copy of this (ask them for an export of metrici.library.products.pmx) and import this with a suitable reference into your own product folder (referred to as product below). To customise this for your own product:

• Remove the contenst of product.library and move your PMX components into here.
• Remove the contents of product.documentation, and put in your documentation.
• Modify product.templates.install.advanced_settings.bindings so that the moduleDefinition binding points to your modfule definition.
• If you don't want installers to be able to modify their instances, remove product.template.install.library. If you want them to be able to modify their instances, retain the library and keep your module definition here and set the moduleDefinition binding to that module definition.
• Modify product.settings.product_builder to give your product name and description. In the dependencies section, list metrici.product.pmx.install as a dependency.