Applications

Top  Previous  Next

What is an mForms Application definition?

An mForms application definition tells mSuite which components of a Notes application to deploy to mobile devices.

There needs to be a definition for every mForms application that you want to deploy.

 

   Deploying the mForms Client

To be able to run mForms application, your users must have an mForms client installed on their device.
Note: mForms is currently only available for Windows Mobile devices.  To deploy the mForms client follow this procedure:

1.Expand the navigation tree to display the User and Groups node.
2.Expand User and Groups to display the group that you want to deploy the application to.  If you want to deploy to an individual user, select the group in the navigation pane, the action pane will display the people in the group.
3.Right mouse click the group or person and choose Properties from the pop-up menu
4.If you are deploying at a person level, check the Show Advanced box on the General tab to display the Application tab.
5.Click the Applications tab.
6.Click the Add... button next to the Deployed packages window.
7.Choose the mForms Client package in the appropriate language from the list.
8.The package will be deployed to the user or members of the group during their next device management session.

 

   Defining an mForms Application

1.Expand the Applications node in the navigation tree, right mouse click mForms Applications and choose New > mForms Application.
2.This will launch the mForms Application Wizard, on the Welcome screen, press Next to continue.
3.On the General Settings, enter a name for your application, the name of the Domino server where the application database is located and the path name of the database.  Optionally you can enter a description of your application.  If you leave the server name blank, mSuite will assume that the database is located on the server running mSuite.  Press Next to continue.
4.On the server Agent Settings page, you can choose Agents from the database to run at the following times - all agents are optional.
Session Start - this agent runs before anything other action take place when the database is replicating.
Pre-replication - this agent runs after new documents have been processed and prior to the replication of existing documents.
Post-Replication - this agent runs when the replication has completed.
Default Open - this runs in the context of each Notes document as it replicates to the device.

 

5.Click Next to continue.
6.On the Form settings page you select the Notes application forms that make up the mobile application:
Shell Form - is the Launch form for the application(s), this usually controls the operation of the application switching to other forms as required.
Push Forms - these are the forms that make up the application.  Once on the device, these will only update if they have been updated (the design is changed) in the Notes application.
Refresh Forms - these application forms are updated on the device during every replication session.  This is usually because the form includes data that is looked up elsewhere and this data may have changed.

 

7.Click Next to continue.
8.On the Agent settings page, you must specify any agents that need to be replicated to the device:
Push agents - these are the agents that make up the application.  Once on the device, these will only update if they have been updated (the design is changed) in the Notes application.
Refresh agents - these agents are updated on the device during every replication session.  This is usually because the agent includes data that is looked up elsewhere and this data may have changed

 

9.Click Next to continue.
10.On the View settings page, you have to specify any views that are used in the mobile application and how they are used:
11.Click the Add... button to add a view.  For each view you need to specify the Server, Database, View and Use.  Views can be in any database, not just the application database.  If you leave the server set to -local-, mSuite will assume that the database is located on the mSuite installation's Domino server (or Notes client).  If you leave database set to -current-, mSuite will assume that the view is in the application database that we are configuring.  Once you have set the server and database field, you can select the view name from the View drop down.
12.Use determines on how the view is replicated to the device:
Local - do not replicate the view contents to the device.  The device can create documents that will show in this view on the device.
Lookup - replicate the view contents to the device for lookup purposes.  The device cannot not add documents to this view.
Both -  combines the attributes of both Local and Lookup views.

 

13.Once you have defined all of the views, click Next to continue.
14.On the Selection formula settings page, you can choose from a list of pre-defined selection formulas that have been defined.  These formulas will be executed to select a set of document to be pushed to the device during replication.
15.Once you have selected the required formulas, click Next to continue.
16.Click Finish to complete the procedure.  The application can now be deployed.

 

 

   Deploying an mForms Application

1.Expand the navigation tree to display the User and Groups node.
2.Expand User and Groups to display the group that you want to deploy the application to.  If you want to deploy to an individual user, select the group in the navigation pane, the action pane will then display the people in that group.
3.Right mouse click the group or person and choose Properties from the pop-up menu
4.If you are deploying at a person level, check the Show Advanced box on the General page to display the Applications tab.
5.Click the Applications tab.
6.Click the Add... button next to the Deployed mForms applications window
7.Choose the application from the list.
8.The mForms application will be deployed to the user or members of the group on their next device management session.

Page url: http://msuitehelp.commontime.com/index.html?ct_adv_mforms_applications.htm