Publish and sign in

When a logic file is ready, you publish it from Metatool, the Windows design tool in Interact. You can publish to Centerpoint, so that Interact servers can use it, or to a Git repository, so that it is kept under version control. Both buttons are on the Solutions tab. Metatool also signs you in to the Doxis services when a feature needs it.

Before you start

• Work against a solution database. The publish buttons are on the Solutions tab and stay grey when no solution is open.
• Save your changes. Metatool refuses to publish while the current document has unsaved changes.
• If a package is open, Metatool warns you that the published file contains the package. Click Yes only if that is what you want.

Publish to Centerpoint

The Publ. to Centerpoint button is enabled when both of these are true:

• The Centerpoint settings are switched on in the Metaforce configuration file. See Configuration below.
• The project is enabled for Centerpoint publishing in the MFSolution application.

To publish:

1. Open the Solutions tab and click Publ. to Centerpoint.
2. Sign in if Metatool asks you to.
3. Type a comment in the Publish comment dialog. The comment follows the release in Centerpoint and helps you recognise the version later, so make it useful.
4. Click OK. Metatool tells you when the logic file is uploaded.

The name of the logic file on the server is set in the MFSolution application.

Publish to Git

The Publ. to Git button is enabled when:

• Git is installed on your PC.
• Git is switched on for the project in the MFSolution application.

To publish:

1. Open the Solutions tab and click Publ. to Git. Metatool connects to the repository and fetches its branches.
2. In the Publish to Git dialog, choose a Branch from the list, or type the name of a new branch. A new branch is created from the main branch of the repository.
3. Type a Comment that describes the change. If you leave it empty, Metatool uses Update followed by the file name.
4. Click OK.

You cannot publish straight to the main branch of the repository, so it is not in the list. A new branch name must follow the Git rules for branch names, for example no spaces and no two dots in a row. Metatool tells you when a name is not allowed.

When the upload works, Metatool shows a message that names the logic file, for example MyLogic.mfl. If it fails, Metatool shows the error in a message box. Metatool also writes a log file named GitTrace followed by a time stamp to its temporary folder, which helps when you need to find out what went wrong.

Open a document in the Editor

Use the Editor button to try a document that has a process list in the Editor, which opens in your browser.

1. Click Editor on the Home or Preview tab. If the logic file has unsaved changes, Metatool saves it first.
2. In the dialog, choose a document. The list shows only documents that have a process list, and the current document is selected.
3. Choose a test data set. When the document has test data connected, that set is already selected.
4. Click Start WebEditor…. If you are not signed in, Metatool asks you to sign in. The Editor then opens in your browser.

The button is enabled when sign-in is set up with CenterpointIdentityUrl, WebEditorEnable is true and WebEditorUrl is set in the configuration file, see Configuration. If something goes wrong, Metatool shows the error in a message box, and it writes a log file to its temporary folder when the document cannot be generated.

Sign in

Click Centerpoint logon on the Home tab to sign in. Metatool opens a browser window where you sign in with your Doxis account. When you are signed in, the status bar at the bottom of Metatool shows the name of your company. The button is enabled when CenterpointIdentityUrl is set in the configuration file, see Configuration.

Metatool asks you to sign in by itself when you have not signed in yet and:

• Audit is switched on and you open a solution.
• You start the Editor.
• You publish to Centerpoint.

Metatool remembers your sign-in session, so while the session is active you are not asked for your password again, also after you restart Metatool. Use the button when you want to sign in in advance, or, if your account allows it, switch to another tenant in Centerpoint.

The first time you sign in there can be a short delay while Metatool creates a folder for cached browser data.

Configuration

The features above are switched on in the file metaengine.config.xml in the Interact bin folder. The keys are:

The addresses in the sample follow the environment you choose above. Use the Centerpoint API address of the same environment for CenterpointUrl.

<add key="CenterpointIdentityUrl" value="https://identity-v2.metaforce.net" />
<add key="CenterpointUrl" value="Address of the Centerpoint API" />
<add key="AuditEnable" value="false" />
<add key="AuditLogUrl" value="https://api.audit.metaforce.net" />
<add key="WebEditorEnable" value="true" />
<add key="WebEditorUrl" value="Address of the Editor API, see the table above" />
<add key="TemplateManagerEnable" value="true" />
<add key="TemplateManagerUrl" value="https://api.interactadmin.metaforce.net" />

The full file, including the path settings, is shown in Documents and templates.

Related pages

• Documents and templates: solutions, packages and export
• User interface: the Home tab
• User interface: the Solutions tab
• Release history