Step Six


Checking Workspace

The workspace and associated directories and files are created in the location you specified on the initial Workspace dialog.

This image shows the Workspace dialog.
Figure 3.6.1 - Figure 12: Workspace dialog.

As a best practice, make a backup of your workspace after it is created. Periodic backups of your workspace should be made especially following significant changes such as adding numerous resources or modifications to existing resources.

Each workspace includes 2 files which are specific to the workspace and Oracle Documaker Studio. They are the *.dxm and *.dxs where * represents the workspace name. For example, if your workspace is named Sampco, you would have a Sampco.dxs and Sampco.dxs file.

These files are located in the root or sandbox of your workspace. They contain configuration information about your workspace. Do not delete these files.

Workspace Structure

The new workspace is created in the location specified in the location setting on the Workspace dialog.

This image shows the Workspace dialog.
Figure 3.6.2 - Figure 13: Workspace dialog.

A directory with the workspace name is created. Subdirectories are created under the workspace directory.

This image shows the Workspace directory structure.
Figure 3.6.3 - Figure 14: Workspace directory structure.
Directory Description
ARC Specifies the location of Archive files such as Archive.car, appidx.dbf\appidx.mdx, catalog.dbf\catalog.mdx, archive.sem
Note: Documaker Studio does not create or modify Archive files
BDFLIB Specifies location for physical group application definition file and application definition file that is checked out of the library
DATA Specifies the location of output files such as errfile.dat, nafile.dat, pofile.dat, etc. created by Documaker Server as defined in the INI <DATA> group.
DEFLIB Specifies the location of files such as font cross reference (*.FXR), optional downloadable font spool, misc. files such as afgjob.jdt, rules.lst, etc.
May also optionally contain physical font files
EDLLIB Specifies the location of the output file when generating normalized AFP or Metacode files
FORLIB Specifies location for physical form and paragraph list files as well as form and paragraph list files that are locked (checked out) of the library
FORMS Specifies location for physical section, style and paragraph files as well as section, style and paragraph files that are locked (checked out) of the library
GRPLIB Specifies location for physical group (form list) files as well as group (form list) files that are locked (checked out) of the library
HELP Specifies the location for optional help files which can be associated with field objects in section or paragraph manager
INPUT Specifies the location of the input file (extract.dat, extract.xml, etc.) used by Documaker Server
MROLIB Specifies the location for MRO (Mobile Responsive Output) files
TABLE Specifies the location of entry tables such as *.dbf\*.mdx or *.tlk
WIP Specifies the location of Wip (work in progress) files including WIP files (Wip.dbf/Wip.mdx), *.pol and *.dat files, afelog.dbf/afelog.mdx and unique.dat for Documaker Desktop.
Note: Documaker Studio does not create nor modifies Wip files.

 

Form.dat to Workspace

In legacy MRLs, the form.dat file defines companies, lines of business, forms and form options for the lines of business, image and image options for the forms and recipients and recipient copy counts.

The form.dat file, along with the SETRECIP.DAT (trigger file) is used as the basis to create the Business Definition File (*.BDF), Form Lists (*.GRP), Forms (*.FOR) and Trigger file (SETRCPTB.DAL).

The output area from the workspace creation process includes an entry for the form.dat file:

[11:00:00AM] Now loading d:\mstrres\sampco\DEFLIB\FORM.DAT. This may take a few minutes.

This image shows the process flow of Form.dat to Workspace.
Figure 3.6.4 - Figure 15: Form.dat to Workspace process flow.

 

The following screen shots map the form.dat component and their workspace counterpart:

Company and Line of Business:

This image shows the Form.dat Company and Line of Business as viewed in legacy Form Set Definition Editor.
Figure 3.6.5 - Figure 16: Form.dat: Company and Line of Business (as viewed in legacy Form Set Definition Editor).
This image shows the Companies and Lines of Business - Business Definition Application file.
Figure 3.6.6 - Workspace: Business Definition Application file (*.BDF) – Companies and Lines of Business.

The output area from the workspace creation process includes an entry for the BDF creation, for example:

[11:03:14AM] Created file C:\fap125\DLL\Sampco1\BDFLib\Sampco1.BDF.
[11:03:17AM] C:\fap125\DLL\Sampco1\BDFLib\Sampco1.BDF

 

Groups:

This image shows the Form.dat Groups as viewed in legacy Form Set Definition Editor.
Figure 3.6.7 - Figure 18: Form.dat: Groups (as viewed in legacy Form Set Definition Editor).
This image shows the Workspace Groups; also referred to as Form List files.
Figure 3.6.8 - Figure 19: Workspace: Business Definition Application file (*.BDF) – Companies and Lines of Business.

The output area from the workspace creation process includes entries for GRP creation, for example:

[11:02:51AM] Created file C:\fap125\DLL\Sampco1\GRPLib\FORMMAKER PACKAGE_GENERAL LIABILITY.GRP.
[11:02:53AM] C:\fap125\DLL\Sampco1\GRPLib\FORMMAKER PACKAGE_GENERAL LIABILITY.GRP

 

Forms and Form Options:

This image shows the Form.dat Forms, Form Options as viewed in legacy Form Set Definition Editor.
Figure 3.6.9 - Figure 20: Form.dat – Forms, Form Options (as viewed in legacy Form Set Definition Editor).
This image shows the Workspace Forms and Form Options.
Figure 3.6.10 - Figure 21: Workspace: Forms (*.FOR), Form Options.

The output area from the workspace creation process includes entries for GRP creation, for example:

[11:00:00AM] Created file C:\fap125\DLL\Sampco1\FORLib\DEC PAGE.FOR.
[11:00:03AM] C:\fap125\DLL\Sampco1\FORLib\DEC PAGE.FOR

 

Images and Image Options or Form Section Options:

This image shows the Form.dat Images, Image Options as viewed in legacy Form Set Definition Editor.
Figure 3.6.11 - Figure 22: Form.dat – Images, Image Options (as viewed in legacy Form Set Definition Editor).
This image shows the Workspace Form and Form Section Options.
Figure 3.6.12 - Figure 23: Workspace: Forms (*.FOR), Form Section Options.

 

Recipients:

This image shows the Form.dat Recipients, Recipient copy count as viewed in legacy Form Set Definition Editor.
Figure 3.6.13 - Figure 24: Form.dat – Recipients, Recipient copy count (as viewed in legacy Form Set Definition Editor).
This image shows the Workspace Form Section Recipient.
Figure 3.6.14 - Figure 25: Workspace: Forms (*.FOR), Form Section Options.

Recipients are also added to the Business Definition File (*.BDF) file with copy count set to Not eligible.

This image shows the Recipient Options with Copy Count set to Not eligible.
Figure 3.6.15 - Figure 26: Recipient Options with Copy Count set to Not eligible.

 

Library Manager

Many resources are stored in the library. They include:

  • Application Definition (*.BDF)
  • Extract Data Dictionary (*.XDD)
  • Forms (*.FOR) Graphics (*.LOG)
  • Groups (*GRP)
  • Scripts \ Triggers(*.DAL)
  • Sections* (*.FAP)
  • Entry Table** (*.TLK)

*When creating a workspace using Release 11.5 or 12.5, Section (*.FAP) and Data Definition files (*.DDT) are merged into the Section (*.FAP) file; the Section file is then imported into the library.

**When creating a workspace using Release 12.5, Entry table files (*.DBF \ *.MDX) are automatically converted to *.TLK files and imported into the library.

The output area includes entries for this, for example:

[11:10:19AM] d:\mstrres\sampco\TABLE\103TEST.dbf
[11:10:19AM] d:\mstrres\sampco\TABLE\ADDRUNIT.DBF
[11:10:19AM] C:\FAP125\DLL\SAMPCO1\TABLE\*.TLK [11:10:19AM] Importing File(s)
...
[11:10:21AM] C:\FAP125\DLL\SAMPCO1\TABLE\103TEST.TLK
[11:10:22AM] C:\FAP125\DLL\SAMPCO1\TABLE\ADDRUNIT.TLK
[11:10:37AM] MDX files
[11:10:37AM] d:\mstrres\sampco\TABLE\103TEST.mdx
[11:10:37AM] d:\mstrres\sampco\TABLE\ADDRUNIT.MDX

hese file types are also stored in the library, but don’t have an equivalent in a legacy style MRL:

  • Paragraphs (*.PAR)
  • Paragraph Lists (*.PSL)
  • Styles (*.STY)
  • Templates (TPL)

You can filter on a specific type in Oracle Documaker Studio Library Manager to display just those file types. For example, you could filter for Sections to display a list of all sections that exist in your library. Resources are displayed in the Library Manager grid. The grid includes information about the resource including its name, type, effective date, version, revision, effective date, locked status (indicates whether the resource is checked out of the library), the ID of the user who created or last modified the resource, description, modified (date and time the resource was checked into the library. It also includes the Mode, Class, Status and Project of the resource; these items are typically used by Project Management.

This image shows the Resource Properties for a Resource.
Figure 3.6.16 - Figure 27: Resource Properties section.

A description of Initial check in is assigned to resources checked into the library by the workspace creation process.

To filter for a specific file type, open the workspace; then open Libraries. Click on the Filter/Search tab. Click in the Type field and select the desired type such as Sections, from the type pick list:

This image shows the Filter/Search tab and its options.
Figure 3.6.17 - Figure 28: Filter/Search tab and its Options.

Click the Filter Now button. System filters for only Sections in the library. A count of those resources that match the defined filter criteria is also shown.

This image shows the Filtered results.
Figure 3.6.18 - Figure 29: Filtered Results.

Click the Reset Filter Options button and then click on Filter Now to set filtering options to defaults.

This image shows the Reset Filter Options button.
Figure 3.6.19 - Figure 30: Reset Filter Options button.

 

Miscellaneous Files

Your MRL may have some files such as miscellaneous text files, batch files, etc. that may not have been copied to the newly created workspace.

Check your MRL against the workspace and copy those files as needed to the workspace.