Adding a form using eChange Man

Creating a brand new form / service / report that has never existed before is a special case in a Configuration Managed environment. When Uniface is using the UD6/CMtool Driver it will always assume that if a ‘file’ does not exist in the ‘reference area’, then it does not exist.

This also applies to a new table / sub-type / library etc, but not a new register, field etc since these exist ‘within’ an existing entity (file).

So the easiest way to create a new form, is to copy an existing form file, remove its contents apart from the header and footer, check it in to eChange Man and then check it out and use it as normal.

e.g.:

New.xml contains:

<?xml version="1.0"?>
<?xml-stylesheet href="components.xsl" type="text/xsl"?>
<?xml-stylesheet href="components.css" type="text/css"?>
<uniface_schema xmlns:html="http://www.w3.org/TR/REC-html40">
</uniface_schema>

To put this source into the eChange Man production area you need to log into the eChange Man client as whoever has access to move something from the Development area to the Production area. You may also have set up rules in eChangeMan to require that another person has to signoff the change before eChange Man will move it from development to production.

From the main screen open up the Areas tree, then the development tree etc. When you find a component to check in, drag it into the CORRECT FOLDER in the production area. If you are prompted for a description, then type a reason for this transfer.

The form can now be checked out and worked on as described previously.

NOTE: Even though there is an XML file, since it is empty of any data, the IDF will not show that the ‘FORM’ exists. Once the XML file is checked out, you can create the ‘FORM’ in the usual manner in the IDF.