Differences between revisions 2 and 3
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * http://linthal.  * http://linthal.softxs.ch/dev/linthal115dev - Development system
Line 12: Line 12:
Fifteen LA2 documents have been taken from the Fifteen LA2 documents have been entered into the system beta and dev systems listed above. The documents are copies of existing document, but example ''vorabzug, zur Freigabe'' and ''gut zur Ausfuerhung'' revisions have been created for all of them, and the ''T)'' and ''T0wv'' dates and other fields have been set in order to provide complete and consistent demonstration data.
Line 14: Line 14:
You can view the documents with the following search:

  1. Change to ''Bereiche'' '''LA2''
  1. DrawMGT meny: '''Dokumente --> Suchen'''
     1. ''Bereich'' - '''Aktueller Bereich'''
     1. ''Kontakt'' - '''213'''
     1. ''Laufnummer'' - '''1000 --> 1020'''

Note that this displays all revisions associated with these documents:

  1. Revision '''v_B''' - ''GA - gut zur Ausfuehrung''
  1. Revision '''v_A''' - ''ZF - zur Freigabe''
  1. Revision '''v__''' - ''VA - Vorabzug''

When you display the revision detail, a new bock is shown which contains the ''user defined fields'' with text describing the fields name and contents.
 
 
Line 16: Line 33:
The following columns are not implemented:

  1. The ''Contract'' menu - The menu is implemented and changed should cause changed to the ''Wer'' menus, but this is not tested, and due to the ''Gruppe'' menu not being complete, will lead to data that causes validation errors on the server.
  1. The ''Gruppe'' menu
  1. Links to ''Grundlagen'' documents
  1. The ''Format'' column
  1. The ''Vorabfug ja/nein'' column
  1. The ''Stn-Nr'' column
  1. The ''Art'' (''Pruefungsart'') column
  1. The ''Pruef-Nr'' column
  1. The ''Q-Eklaerung'' column
  1. The ''Verteiler gut zur Ausfuerhung'' columns ''etc'' and ''Ablage/Archiv''

The following features are not completely implemented and/or tested:

  1. Client side cross-field validation of workflow steps. E.g. there is no checking when you make a workflow step update to make sure that the preceding and subsequent workflow steps have are compatible with the change.
  1. The server-side ''revision date'' is not set, this is bacause a race condition can occur which causes server-side validation error
  1. The update count is implemented but not completely tested, it is not recommended to do simultaneous updates on the server and client. Do a refresh in Excel if you update records on the server.
Line 17: Line 54:

This section describe operations that can be performed for the demo:
Line 97: Line 136:
=== Restrictions == === Restrictions ===
Line 103: Line 142:
  1. Do not change   1. Do not change ''Ver'' (revision code)
  1. Do not copy and paste rows of data

Excel Integration - Axpo Demo Notes

Contents

  1. Excel Integration - Axpo Demo Notes
  2. Systems
  3. Test Data
  4. Limitations of the Excel VBA Code
  5. Demo Script
    1. Startup
    2. Menu Items
    3. Login
    4. Search for and Display Data
    5. Updating Data and Saving It to Server
      1. Scenarios
      2. Restrictions
    6. Refresh Data
  6. Compatibility Testing Notes
    1. Excel Versions
    2. Windows Versions and Languages

Systems

Test Data

Fifteen LA2 documents have been entered into the system beta and dev systems listed above. The documents are copies of existing document, but example vorabzug, zur Freigabe and gut zur Ausfuerhung revisions have been created for all of them, and the T) and T0wv dates and other fields have been set in order to provide complete and consistent demonstration data.

You can view the documents with the following search:

  1. Change to Bereiche LA2

  2. DrawMGT meny: Dokumente --> Suchen

    1. Bereich - Aktueller Bereich

    2. Kontakt - 213

    3. Laufnummer - 1000 --> 1020

Note that this displays all revisions associated with these documents:

  1. Revision v_B - GA - gut zur Ausfuehrung

  2. Revision v_A - ZF - zur Freigabe

  3. Revision v - VA - Vorabzug

When you display the revision detail, a new bock is shown which contains the user defined fields with text describing the fields name and contents.

Limitations of the Excel VBA Code

The following columns are not implemented:

  1. The Contract menu - The menu is implemented and changed should cause changed to the Wer menus, but this is not tested, and due to the Gruppe menu not being complete, will lead to data that causes validation errors on the server.

  2. The Gruppe menu

  3. Links to Grundlagen documents

  4. The Format column

  5. The Vorabfug ja/nein column

  6. The Stn-Nr column

  7. The Art (Pruefungsart) column

  8. The Pruef-Nr column

  9. The Q-Eklaerung column

  10. The Verteiler gut zur Ausfuerhung columns etc and Ablage/Archiv

The following features are not completely implemented and/or tested:

  1. Client side cross-field validation of workflow steps. E.g. there is no checking when you make a workflow step update to make sure that the preceding and subsequent workflow steps have are compatible with the change.

  2. The server-side revision date is not set, this is bacause a race condition can occur which causes server-side validation error

  3. The update count is implemented but not completely tested, it is not recommended to do simultaneous updates on the server and client. Do a refresh in Excel if you update records on the server.

Demo Script

This section describe operations that can be performed for the demo:

Startup

The following three files should be installed in the same directory:

  1. LinthalDrawMGT-Template-1.xlsm - An example planning workbook

  2. LinthalDrawMGT-Menu-1.xlsm - Lightweight AddIn that installs the DrawMGT Excel Ribbon (menu)

  3. LinthalDrawMGT-Template-1.xlsm - VBA AddIn that contains the library code that implements the Excel Interface

Procedure

  1. Open the Template file:

  2. Watch in the lower message are and verity that Excel opens the Menu and Lib files

  3. Excel will display an example document list and a number of hidden worksheets (these worksheets will not be displayed in the production version).

  4. Verify there is a new Ribbon (menu item) called DrawMGT next to the Start menu.

  1. Server

    1. Login - Login into the DrawMGT server

    2. Logout - Logout from server

    3. Set Server - not enabled demo

  2. Data

    1. Search Documents - Displays a search form. See below for details

    2. Refresh Attributes - not enabled for demo

  3. Edit

    1. Get Next Sequence - not enabled for demo

    2. Refresh Selected - Refresh selected rows (local data) with latest data from server

    3. Refresh All - Refresh all rows (local data) with latest data from server

    4. Duplicated Selected - not enabled for demo

    5. Check for Duplicates - not enabled for demo

  4. Save

    1. Save Selected - Save all rows to server (see below)

    2. Save All - Save selected rows to server (see below)

  5. Test

    1. Test Cases - Displays a list of regression test cases (do not use)

Operations on all and selected rows:

  • All Rows - Operation works on all rows in the spreadsheet

  • All Rows - Operation works on rows where any cell is selected in the spreadsheet. The selection does not need to be contiguous.

For both cases the header rows and empty rows are ignores.

Login

  1. Select menu item: DrawMGT --> Login

  2. Enter DrawMGT user name and password
  3. A confirmation dialog is presented if the login is successful

Search for and Display Data

  1. Select menu item: DrawMGT --> Search Documents

  2. A search dialog is displayed: Enter the following search criterion:

    1. Rapport - Select Bau

    2. Bereich - Select LA2

    3. Kontakt - Select 213

    4. Laufnummer - Select 1000 --> 1020, or select a smaller range (2002 -> 2006) if you want quicker results.

Note that the search and display of data is slow, and that a number of hidden rows and columns are displayed during the processing period. This is because the Excel screen updating is enabled (to assist the testing and development process).

After the search processing completes, the hidden cells and rows are hidden, and a list of approximately 15 documents is displayed.

The header contains sections for the document and the vorabzug, zur Freigabe and gut zur Ausfuerhung revisions.

Updating Data and Saving It to Server

You can change data for documents

Scenarios

  1. Change the value of the T0 field and observe that the other Soll dates change.

  2. Change the value of the Delta fields and observer that preceeding SOll dates change.

  3. Set the Ist date for the Vorabzug Erstellen

  4. Set the Ist date and Status (to non-Offen) for the Vorabzug Stellungnahme

    1. You can also change the Wer columns. Note that the user list is displayed based on the user roles in the server

  5. Change the values in the Resourcenplannung and Verteiler. Notes:

    1. The Resourcenplannung von and bis dates are calculated base on the T0 value and should not be changed manually.

    2. The gut zur Ausfuerhung fields: Verteiler-Ext and Verteiler-Ablage are not process correctly (a bug)

Restrictions

Given the limited test data observe the following restrictions:

  1. A document code, you can demonstrate the document classification menus, and that the document code is automatically updated basedon the menu setings and Laufnummer and Teil, but don't save the document if the code is changed (this has not been extensively tested).

  2. The Bereich or Gruppe - These menus are not completely implemented

  3. Do not change Ver (revision code)

  4. Do not copy and paste rows of data

Refresh Data

Compatibility Testing Notes

Tested with:

Excel Versions

  • Excel 2007 and Excel 2010.
  • Not tested Excel 2003

Windows Versions and Languages

  • Windows XP, Hungarian
  • Windows 7, English and German

ExcelIntegrationAxpoDemoNotes (last edited 2011-06-06 14:14:11 by alan)

Copyright 2008-2014, SoftXS GmbH, Switzerland