Connector for dg archive in processes
User Switch Action
Since processes do not support interactive user logins to third-party systems, the process must first log in to dg archive before triggering dg archive actions. There are two different options available for this purpose, which allow you to select an additional user specified in the dg archive configuration for authentication. For timer-controlled data group processes, the user can be selected directly in the timer configuration. The " Switch User" action offers another option. This allows you to switch to the dg archive user within a process.
To do this, create a new user switch action and select "dg archive" as the action type.
In the next step, you can select the user under whose account the following actions are to be performed. You can find information about the settings in this dialog box here.
Time Stamp Data Synchronization
Unlike files, the stamp data for a document saved in dg archive via Intrexx is stored in the Intrexx data group fields. If a document's stamp data is modified directly in dg archive, it cannot be automatically synchronized with Intrexx immediately. Therefore, Intrexx automatically updates the fields of a dg archive stamp as soon as the record is opened on a view or input page. To save the current data in Intrexx as well, the user must then click "Save." This process can also be automated using a process, so that the metadata of an Intrexx data group can be synchronized with the objects in dg archive at regular intervals.
To do this, create a new process with a time-based event (Global Timer). In the timer configuration dialog, select the "dg archive" data group and define a filter if necessary.
In the next step, you must select a user for whom static login credentials have been stored in the dg archive configuration.
Now connect a new data group action (the "Change Record" action) to the timer event handler.
The same data group as the one selected in the timer is selected as the target data group.
Here, select the "Simple Filter" option. The two ID fields are selected as the data fields in both the destination and source data groups.
In the field mapping, you can now assign the fields from the source data group to the target data group for which the dg archive stamp data is to be re-read and saved. Please note that the file fields must not be synchronized here, as this will otherwise create a new version in dg archive. Click "OK" to confirm the dialog box and save the process. When the records are imported from the source data group, the data is re-read from dg archive and, in the next step, saved back into the assigned data fields in Intrexx.
File Transfer Between Intrexx and dg archive
Typically, files and documents are stored physically only on the dg archive server and are loaded by Intrexx at runtime when a user accesses a dg archive file in the portal. In some cases, it may also be useful to transfer files from dg archive to Intrexx or to copy existing files from Intrexx portals to dg archive. To do this, file fields can be mapped between Intrexx and dg archive data groups using data group actions. If data is read from a "dg archive" data group and written to an Intrexx data group, the files from "dg archive" are copied to the Intrexx Portal Server. Conversely, files can be copied from Intrexx applications to dg archive by reading from an Intrexx data group and writing to a dg archive data group. By applying filters to the source data set, you can specify which data records—and thus which files—should be transferred to the respective target system. The following example illustrates how to transfer files from Intrexx to dg archive:
First, the timer reads the data records from an Intrexx data group. Next, a user switch operation is performed to log in to the dg archive server. After that, the files and metadata from the Intrexx data group fields are transferred to dg archive using a dg archive data group action. The field mapping is as follows:
Importing and Exporting dg archive Configurations
dg archive configurations are automatically included in a portal export and recreated during import. If you want to export a single configuration to another portal, this is currently only possible via the file system.
The configuration files are located in the internal/cfg/dghyparchive directory within the portal directory. Each configuration consists of an XML file, and the file name corresponds to the configuration GUID.
If you want to transfer a configuration to another portal, simply copy the corresponding file and paste it into the same subdirectory on the destination portal. After restarting the portal server, the configuration will be available in the Integration module.