VISUAL PLANNING 5.3 DOCUMENTATION

Export Events

DEFINITION

This functionality allows to export a group of events from a VISUAL PLANNING planner to an external destination.

An events export is done into a unique destination that may be:

  • A *.CSV file
  • A *.XLS or *.XLSX sheet (or a tab)
  • A database table:
    • MYSQL,
    • ORACLE,
    • SQLSERVER,
    • or MSACCESS.

PREREQUISITES

Technical requirements

Technical Requirements vary depending on the technology used for the destination.

The main one being that the destination exists and VISUAL PLANNING accessed correctly.

Other prerequisites may appear depending on the trigger used to start the export.

Functional requirements

This tool does not need any essential requirements.

However, for a good use, it is useful to create:

This heading can store the date, the hour of the last export, the login and the name of the context.

SETTINGS

It is required to save context settings before use. (c.f. Use).

Create an events export context

To create a new events export context, go to the Global settings panel > Right-Click on Export events > Create an Events export context.

The lower part is then activated:

Specify the import settings, then click on:

  • OK to save the context,
  • Restore to undo.

These settings are:

Name

This is the Name of the import context.

Description

This is an optional Description of the context.

History

This non-editable parameter store the date, time and login of the last modification of the context.

Definition

This is the Definition of the context.

cf. Definition of context to export events

Mark the treatment

This checkbox allows, if selected, enable the option to insert date, hour, and name of the context in exported events.

cf. Use below

"URL" call

The option “URL” call triggers outside VISUAL PLANNING the implementation of this import context following a defined syntax.

cf. Exports & imports by URL

Event's creation/modification

This box enables the triggering of context during the creation and/or modification of events.

cf. Automatic Exports and Imports

Activated

This check box enables the trigger of service import.

cf. Export using service

Triggers

This option allows to define triggers in the case of import by service.

cf. Export using service

Reporting activated

This check box allows to send an email report of the result of each triggered import.

Prerequisites: The SMTP server must be configured because it is automatic mails. cf. Automatic sending of e-mails

Sender

It is the email considered as the sender when reporting by mail.

This parameter is active and required if Reporting activated is checked.

Recipients

This is to specify email addresses to be defined as recipients during the reporting by email.

This parameter is active and required if Reporting activated is checked.

Modify an events export context

To modify an events export context, go to the Global Settings panel, Right-Click on the context to modify it.

The lower part of the panel is then activated. Modify the settings (cf.Create an events export context), then click on OK to save the modifications.

Duplicate an events export context

To duplicate an events export context, go to the Global Settings panel, Right-Click on the context > Duplicate.

The lower part of the panel is then activated. Modify the settings of the duplicated context (cf.Create an events export context), then click on OK to save the modifications.

Delete an export context

To delete an events export context, go to the Global settings panel > Right-Click on the context > Delete.

The following message appears:

Then click on:

  • Yes to definitely delete the context,
  • No to cancel the deletion.

USE

Trigger

Mark the treatment

If the context marks the treatment, the history and the name of the context are stored in the exported event:

  • in a form heading called VPEXPORT, if it exists (cf. functional requirements above)
  • in the event note si the form heading doesn't exist
Print/export
Languages
Translations of this page: