29.4.3. Specifications

<< Prev   Next >>

29.4.3.1. Reports

You can generate reports on a mobile platform in two different ways:

• Process existing data and generate an actual report in 1C:Enterprise language.
• Implement a form on a mobile platform, use this form to set up report generation parameters (filters, and so on), and pass the actual generation process to a remote system, which will return a spreadsheet document for display on a mobile device.

Select one of these options based on a certain set of factors:

• Availability of all the data required to generate a report in the mobile application infobase.
• Availability and quality of the communication channel between the mobile device and the remote system.
• Report complexity.
• Exchange structure with the remote system.
• Planned report operations.
• Other specifics.

If you decide to generate a report on a mobile device, remember about the mobile platform features. You can use datasets to obtain data and software that generates spreadsheet documents (based on the template) and charts (if required) to build a report.

If permanent high-speed communication channels with a remote system are available for the mobile application, which has all the necessary data to generate the required report, you can implement only the interface part of the report (setting filters, decryption processing, and so on) for the mobile application. In this case, the report will be generated in a remote application, and the finished report will be returned to the device for display.

All intermediate options are possible as well. For example, if periodic exchange is implemented, you can generate report settings on a mobile device, pass them to a remote system during an exchange session, and get the generated report back for display.

To interact with a remote application, you can use a Web-service (which provides the remote application), exchange data using an exchange plan, and so on.

If you need to implement decryption of a report, keep in mind that a mobile application alone can only review the values specified as decryption of a report cell. The remaining actions must be implemented programmatically, which includes getting a new report option with applied filters, and so on.

29.4.3.2. Operation with roles and users

When you set up roles in a mobile application, remember that of all the access rights provided by the platform for personal computers, only a limited set is available on the mobile platform. This set of rights ensures functioning of various features that keep the mobile application interface operable. The rights that can be used on the mobile platform are marked with an asterisk in the full list of rights.

There is also a feature to set up a form and role visibility of the command interface based on roles.

Privileged mode management methods in the mobile platform are used for compatibility with the platform for personal computers. The calls of privileged mode methods are ignored by the mobile platform.

When defining user access rights, the standard scheme is applied: if no users are specified in the infobase, the DefaultRoles configuration property is used to define access rights. If a user is used to access mobile application data, access rights are determined by the components of the user's roles.

The mobile platform has a limited set of tools for operations with infobase users:

• Only one user can exist in the infobase. If you attempt to create more than one user, an exception is thrown.
• You can create a user only programmatically. If you create a user interactively in Designer, such user will not be transferred to the mobile device.
• The mobile platform does not offer authentication tools when starting a mobile application. If the user is listed in the user list, this user will automatically be set as the user of the current session.

As a result, we can recommend the following scheme of operation on behalf of users with different rights:

1. The user is created with the required set of roles, or the set of roles of the existing user is changed.
2. The mobile application is restarted using the Exit(False, True); structure.

29.4.3.3. Full-text search

Full-text search in the mobile platform is described in the respective section.

<< Prev   Next >>