8.4.2. IM-Workflow¶

8.4.2.1. There are limitations when system locale is added.¶

• If you try to restart the system operation right after the change of locale, mismatch with both the master data and transaction data will occur.

  If you try to approve the matter after changing the locale, normal process does not take place, and data may be destroyed.

  
  

  You can make a recovery by doing the following steps only if you have added the locale (it does not apply to the deletion of locale).

  • With regard to master data, data for the amount of added locales should be prepared.

  • With regard to the transaction data applied before the change, you need to switch back to the user locale before the addition, and perform the operation.

    Data which was applied after the addition of locale can be operated by any user locale.

8.4.2.2. Master data is required for each system locale.¶

• Master data would be required for each system locale in IM-Workflow.

  You cannot do the operation with only the Japanese as master data, when 3 languages

  (Japanese, English, Simplifiied Chinese) are available for the system.

  
  

  Registration of master data is necessary for the following for each locale.

  
  

  ・Role Information

  
  

  ・IM-Common Master Information

  1. User

  2. Department

  3. Company + Post

  4. Public Group

  5. Public Group + Role

  
  

  ・IM-Workflow Master Information

  1. Matter Property Definition

  2. Rule Definition

  3. Mail Definition

  4. IMBOX Definition

  5. List Display Pattern Definition

  6. Flow Group Definition

  7. Contents Definition

  8. Route Definition

  9. Flow Definition

8.4.2.3. Sizing of storage region is necessary depending on the master setting of workflow.¶

• Data is stored into Database and Storage in IM-Workflow.

  
  

  Therefore, server resource of Storage would be required as the volume of data increases.

  [*] Data stored in Storage would increase proportional to the “Number of Nodes” and “Number of Actions”.

  
  

  Please size the Storage area based on the examples below:

  * Number of Nodes: 5 ([Start]→[Apply]→[Approve]→[Approve]→[Approve]→[Approve]→[Finish])
  * Number of Actions : 5  ⇒ 200KB
  * Number of Actions : 10  ⇒ 360KB
  
  * Number of Nodes : 10 ([Start]→[Apply]→[Approve]→[Approve]→・・・・・→[Approve]→[Approve]→[Finish])
  * Number of Actions : 5 ⇒ 400KB
  * Number of Actions : 10 ⇒ 730KB
  
  [*] The example above is the case where file transaction level (transaction-file-level) is 1.
  

8.4.2.4. It is necessary to adjust the server setting etc. depending on the master setting of workflow.¶

• [Image Output] function of [Flow Reference] screen and API[WorkflowImageManager] will consume memory, which is proportionate to the number of nodes in the Flow Diagram (Route Diagram).

  Therefore, “Out of memory” may occur if you place too many nodes. In this case, please review the setting of server, and make necessary modifications.

8.4.2.5. Process time will increase proportionate to the number of nodes that are set in the route definition.¶

• When you set the following nodes in Apply/Approve process, process time will increase proportionate to the number of nodes that are set.

  • [Vertical Placement]
  • [Horizontal Placement]
  • [Dynamic Approval]

8.4.2.6. Target users will be removed depending on the contents of route setting.¶

• Target users are removed on [Route Setting - Version - Edit] screen in the following cases.

  In these cases, please set the target users after connecting the node.

  • After you place the [Approve Node] and set the target users, if the Apply/Approve node is connected to this node, target users are removed.

  • In case the route (connection) such as [Apply/Approve Node]-[Approve Node] exists,

    if you change the route (connection) like [Other than Apply/Approve Node]-[Approve Node], target users for [Approve Node] are removed.
  • In case the route (connection) such as [[Other than Apply/Approve Node]-]-[Approve Node] exists,

    if you change the route (connection) like [Apply/Approve Node]-[Approve Node], target users of [Approve Node] are removed.

8.4.2.7. There are remarks when operating matters in the route definition that includes synchronous node.¶

• In the route definition that involves synchronous node, if the move from outside-synchronous to inside-synchronous is made by the matter operation,

  even if all the inside-synchronous routes reach synchronous combined node, they will stop at synchronous combined node.

  (In this case, they do not proceed to the next node of synchronous combined node).

8.4.2.8. There are items to be noted about the display of flow reference.¶

• If you click the [Image Output] button before all the Flow Diagrams (Route Diagrams)are displayed on the [Flow Reference] screen,

  flow diagrams (route diagrams) are not dispalyed.

  
  

  This phenomenon could be avoided as follows.

  By clicking the [Latest Information] button, you can re-display the flow diagram.

8.4.2.9. In some cases 2 process request emails are sent to the delegated user.¶

• In the delegation setting, if the user who is set for delegation has process authority, 2 process request emails will be sent.

8.4.2.10. Sometimes normal email transmission fails depending on the mail server used.¶

• If you omit the subject or mail body in mail definition, emails are sometimes not submitted. This depends on the mail server in use.

8.4.2.11. Mail address which is set in the user profile will be used for mail destination.¶

• Mail address which is used for mail transmission would be only the [Mail Address 1] which is set in the user profile.

8.4.2.12. Saved node setting may not be sometimes reflected correctly on the Matter Handle - Node Edit screen after application is made.¶

• If you place the template replacement node (first node in template = approve node) immediately after the Apply Node or Approve Node,

  setting of saved node will not be correctly reflected on Matter Handle - Node Edit screen after the matter application.

8.4.2.13. Standard process name will be displayed as process name of process history that was processed before redeployment.¶

• If the horizontally/vertically-placed node which was already deployed is re-deployed, since the node ID is changed, process name of process history that was processed before re-deployment would be the standard process name.

8.4.2.14. Automatic approval will not be made for the node where re-process automatic approval is set for arrive process.¶

• If the horizontally/vertically-placed node which was already deployed is re-deployed, since the node ID is changed, automatic approval will not be made for the node where re-process automatic approval is set for arrive process.

8.4.2.15. If you click the status confirmation icon of process target plug-in for the predecessor process of node setting screen, HTTP500 error may result.¶

• On the node setting screen of deployed vertically/horizontally-placed node, if the process target setting is dependent on the previous processor like [XXX of Previous Processor], following error screen is displayed when the status confirmation icon is clicked.

  “HTTP 500 : Error occurred in the Server.”

8.4.2.16. If the process time limit automatic process batch is executed on Hanko imprint project, automatic process will fail.¶

• In using the Hanko imprint function if the process that requires Hanko is done by the process time limit automatic process batch, process will be executed by the system user (imw^system).

  Therefore, it would not be possible to obatin the Hanko for usual use, action process results in error, and automatic process fails.

  
  

  <*> System user (imw^system) uses the prohibited character (^), which cannot be registered by IM-Common Master as the user code.

8.4.2.17. Asynchronous Client object cannot be used for the process on standard screen.¶

• If asynchronous is used for the process on standard screen, Clent object cannot be used for the action process and arrive process in script development model.

  If HTTP object information is needed, implementation on Java would be required.

8.4.2.18. Since the node setting information remains in the copied flow definition, the message “Setting is removed.” will be displayed if you do the import.¶

• If you do the import after editing the copied flow definition, route definition, and contents definition,

  a message “Setting is removed.” might be displayed.
  [Cause]

  Some of the node setting information would remain by editing, and this phenomenon might occur, if the import check condition is met.

  (Node setting information remains so that information before the edit can be restored.)
  [Operation]

  This phenomenon occurs if you do the following operations :

  1. Create Contents Definition_A, Route Definition_A, Flow Definition_A, and Rule Definition_A.
  2. Make a copy of each definition _ Contents Definition, Route Definition, and Flow Definition _ on each version edit screen.
  3. Create Rule Definition_B.
  4. Delete Rule Definition_A, which is set in Contents Definition_B.
  5. Newly create Rule Definition_B which is set in Contents Definition_B.
  6. Newly add Rule Definition_B to Flow Definition_B.
  7. Run export process for Contents Definition_B, Route Definition_B, Flow Definition_B, and Rule Definition_B.
  8. Import the exported data.

  [Effect]

  Since the internal information merely matches with the import check conditions, there is no impact to the import process in this case.

8.4.2.19. There are reminders about the asynchronous process on standard screen.¶

• If the process synchronous/asynchronous setting on the standard screen is set to asynchronous,

  there are times when the IM-Workflow process is not performed correctly in such a case as server stoppage during asynchronous process.
  If there is any interrupted IM-Workflow process, “Asynchronous Process on-going” information is displayed on [Asynchronous Process Status] screen.

  In this status the matter is locked, and so it cannot be processed or approved.

  By deleting the “Asynchronous Process on-going” information on [Asynchronous Process Status] screen, the matter lock status is released.

  When you restart the server, please do it after the process of IM-Worklfow has completely ended.
  If it is inevitable from the operation viewpoint that you should restart the server during the workflow process, please set the settings of workflow parameters [Synchronous/Asynchronous Setting of Process on Standard Screen]

  and [Matter End Process, Reach process, Mail Send Process, IMBox Send Process Synchronous/Asynchronous Control] to Synchronous.

8.4.2.20. There are reminders about references to HTTP objects in Asynchronous Action Process and Arrive Process on standard screen.¶

• With regard to the asynchronous process on standard screen, IM-Workflow process and Action Process / Arrive Process are executed by separate threads.

  Information stored for the user contents to HTTP-type objects such as HTTPContext and HTTSession are executed by separate threads.

  They cannot be used (referenced) by IM-Worlflow process or Action Process / Arrive Process.

  In the action process / arrive process, it is recommended to pass the value by workflow parameters.
  In consideration of the implementation situation in which the application uses HTTP-type object,

  a mechanism that would make HTTP-type object accessible from action process / arrive process is also offered.

  However, since this implementation is deprecated, warning log will be displayed.

8.4.2.21. Process request message is distributed in the locale of the user for whom the processing was made.¶

• Process request message is sent to the process target user of the next node after making the approval process and so on.

  At this time the subject and body of the message are sent in the locale of the user who performed this process (approval etc.).

  
  

  This specifications would apply to the following :

  1. Mail

  2. IMBox (ApplicationBox)

  3. IM-Notice

Smart Phones

8.4.2.22. If the PC-version user contents are displayed on iPhone, Android smart phone, or Android tablet, operations may become unstable.¶

• In case IM-Workflow PC version is used, GreyBox does not support the display on iPhone, Android smart phone, or Android tablet.

  
  

  Therefore, if you set the PC version user contents as the screen for smart phones in contents definition, and if you process the matter by using PC version contents on smart phones, screen which is displayed by GreyBox would become unstable.

  (For details about setting the PC version user contents for smart phone screen, please refer to “IM-Workflow Programming Guide”.)

  
  

  Each process screen (Apply/Re-Apply/Apply(not yet applied)/Temporary Save/Process/Confirm) displayed on GreyBox, and the node setting screens to which these screens will transition have the following limitations as far as our company knows today.

  
  

  • When you display GreyBox initial time, it is recommended that you display with no zoom.
    • If you initially display GreyBox in a zoomed state, display area of GreyBox may become too narrow.
  • If you tap the input item, input item on the screen displayed at the under-layer of GreyBox may be focused.
  • Depending on the screen operation, part of the gray-out area of GreyBox may be released allowing the operation at the under-layer of GreyBox.
  • Depending on the screen operation, GreyBox extends beyond the browser display area, and access to the input items may not be possible.
  • Even if you tap the file name of the uploaded file, download of the file does not take place.
  • Concurrent upload of multiple files may not be possible on some devices. You can upload one at a time.
  • Display of select boxes that allow multiple selections such as mail destinations of negotiation mail will be different from that on PC version.
    • Display depends on the browser of the device in use.
  • Confirmation dialog which is usually displayed before process is displayed near the center location of GreyBox. Therefore, if the confirmation dialog is not focused, it may be hard to find where the dialog is displayed. Or, if the confirmation dialog is focused, it may be hard to find the current location.
  • If the exception occurs while executing the process, error dialog is displayed in the upper part of GreyBox. If the upper part of GreyBox is not contained in the display area of the browser, you may not be able to notice that the error log has been displayed and may perceive it as no response.
  • If you do the scroll operation in GreyBox, depending on the devices used, the upper edge of GreyBox is forced to automatically match with the upper edge of the browser display area.
    • In this case please access the target item after setting the zoom to minimum (no expansion), or repeat the scroll several times.
  • If you change the selection value of [Saved Setting] on Node Setting screen, screen will be reloaded, but the selection menu of [Saved Setting] will remain displayed on the screen.
    • This is just an appearance issue on the screen. Changing the selection value after the screen is reloaded has no effect.

  Among the items listed above, if the display of GreyBox screen becomes invalid (e.g. screen slips out of the browser etc.), following measures should be taken.

  • Set the zoom to minimum (no expansion), and scroll the screen display to the upper left corner.

    Display position mismatch on GreyBox may possibly be resolved by this operation.

    If this 1 operation does not resolve the problem, repeat the zoom → minimize → scroll operation.

  In case you need to set the PC-version user contents to the screen for smart phones, please be aware of the following notes about user contents.

  • PC-version UI components have not been verified in smart phone environment.
  • If you are using PC-version UI components in PC-version user contents, screen display or operation may not be performed correctly.

8.4.2.23. We do not guarantee for operations if URL is directly specified.¶

• If you reload (refresh) the URL which is directly specified or displayed as a URL of the browser on smart phones, operations cannot be guaranteed.

  You may not be able to tap the button or some unexpected result may happen.

8.4.2.24. In case spWorkflowOpenPage tag is used, it should be placed inside the element that specifies data-role=”page”.¶

• Please place the <imart type=”spWorkflowOpenPage”> tag inside the element that specifies data-role=”page”.

  Please specify ID attribute as an element.

  
  

  When the [Back] button is clicked on the process screen, ID of the corresponding element is obtained/specified, and screen transition will occur.

  If the <imart type=”spWorkflowOpenPage”> tag does not exist inside the element that specifies data-role=”page” or if there is no ID attribute for the corresponding element, screen transition by the [Back] button on the process screen is not possible.

8.4.2.25. There are limitations about the User Contents Screen ID.¶

• On the IM-Workflow smart phone process screen, screen transition using Ajax is provided.

  Therefore, on the screens such as user contents screens that are linked with IM-Workflow smart phone process screen, care should be taken so that the ID attribute of the pages do not duplicate.

  
  

  Shown below are the values of ID attribute which are defined on IM-Workflow smart phone process screen.

  • apply
  • temporary_save
  • approve
  • reapply
  • unapply
  • confirm
  • node_config_single
  • node_config_multi
  • department_config
  • department_and_post_config
  • post_config
  • public_group_config
  • user_config
  • apply_list_search
  • process_list_search
  • confirm_actv_list_search
  • confirm_cpl_list_search
  • transfer

8.4.2.26. If the attachment file is displayed on the matter detail screen, you cannot return to the matter detail screen, because there is no Close button.¶

• This also applies to the case in which image output is made from the flow reference screen. If image output is made, you cannot return to the flow reference screen.

8.4.2.27. On the flow reference screen, scroll bar of the table that shows process date/time, node name, and so on is not displayed.¶

• Since the screen for PC is displayed, screen display on smart phones may not be correctly performed.

8.4.2.28. User contents cannot be set for each node in case of smart phones.¶

• In the smart phone version, even if there are multiple user contents (screens) in contents definition, only the one for [Initial Use] will be effective.

  In the PC version, you can set the user contents screen for each node in the flow definition.

8.4.2.29. Negotiation mails for process and pull back cannot be sent.¶

8.4.2.30. With regard to the attachment file, only the file types that the device browser supports can be downloaded and displayed.¶

8.4.2.31. In case iPhone is used, workflow matter number is recognized as a telephone number.¶

8.4.2.32. If the process that does not use user contents is made on smart phones, user parameters cannot be passed to the action process.¶

• If the action for no user contents is set to [skip],

  user parameters cannot be passed to the action process unless the process is made through user contents on smart phones.

  
  

  2013 Spring version allows user contenst to be defined for smart phones.

  Setting value for the action for no user contents (error or skip) has been also provided.

  If you set the action for no user contents to [skip], it is the same as the behavior for 2012 Winter or before.

8.4.2.33. Attachment file of application screen cannot be deleted on NTT Docomo GALAXY SⅡ LTE SC-03D.¶

• [Phenomenon]

  Attachment file of application screen cannot be deleted on NTT Docomo GALAXY SⅡ LTE SC-03D.
  [Condition]

  Steps for Reproduction

  1. Open the application screen for the flow in which file can be attached on Galaxy SII.

  2. Upload 3 arbitrary image files.

  3. Delete 1 image file before application is made.
  Symptom]

  [Parameters passed as argument are invalid] error will occur, and file cannot be deleted.
  [Circumvention]

  This problem may occur when the screen display is not completed because of network delay or slow server performance.

  Please upload the attachment file after the display of application screen is completed.

8.4.2.34. After the confirmation process, same matter is displayed in the list as not confirmed.¶

• If you set the process setting to asynchronous on standard screen and do the confirmation, screen switches immediately after the confirmation, and the list is displayed.

  Since the confirmation process is to be executed asynchronously, confirmation process may not have been completed when the list is displayed.

  
  

  In this case, same matter is displayed in the list as not confirmed. Since you can do the confirmation process again,

  there is a risk of doing the confirmation process twice.

  
  

  [Circumvention]

  After you do the confirmation, please check the staus of asynchronous process by [Process Done]- [Process Status Tab], see the confirmation process status,

  and avoid doing the confirmation process multiple times.

8.4.2.35. There are remarks when registering the user contents with [Apply] screen type to My Menu.¶

• Menu items that can be registered to My Menu are basically the ones that exist in the site map.

  As an exception user contents screen that has [Apply] as a screen type can be registered to My Menu.

  In this case my menu can be used only by the standard process screen (the screen that states IM-Workflow tag lib [workflowOpenPage]).

  If you register user contents screen that has a screen type other than [Apply], access from My Menu will not work properly.

8.4.2.36. If system error occurs while processing [Matter End Process/Arrive Process/Mail Send], memory may not be released.¶

• In the [Matter End Process/Arrive Process/Mail Send] process of IM-Workflow, context information is put into persistent memory while processing,and the memory is released after the process is completed.

  If system error occurs during the [Matter End Process/Arrive Porcess/Mail Send] process, and the process ends abnormally, memory may not be released.

  Memory constraints might occur if such system errors are repeated, and therefore Web Application Server should be restarted to release the memory.

8.4.2.37. Subject department on the Standard Process Screen may not be initially displayed.¶

• When current department (belonging department on the upper right of General User Screen) in the utilitty menu is changed, it will be initially displayed in the subject department on the Standard Process Screen in this release.

  In the specifications above, subject department may not be initially displayed on the standard process screen.

  ・If the department that matches with the current department in the utility menu does not exist in the subject department, it will not be initially displayed.

  This is caused by the fact that only the default department set can be set as current department in the utility menu, while department other than default department set

  can be set as standard department in IM-Workflow flow definition.

  ・Department name which is different from the one selected for current department in utility menu may be initially displayed as a subject department.

  Current department in the utility menu has the name on the system date, and the one for IM-Workflow has the name based on the application base date.

  If the term setting is done for the department, name at the system date and the name at application base date could be different.

8.4.2.38. If the node is restored by Pull Back after Send Back, process target user will resume to the one before replacement.¶

• There are remarks about the process target user of node that is restored by pull back after send back.

  
  

  In case there are multiple routes within the branch, if Pull Back is made after doing the Send Back from the node on one route to outside the branch,

  restoration process of node on the other route is executed.

  If the process target user of the node waiting for restoration process has been replaced, restoration would be conducted as follows :

  
  

  ・In case the process before restoration is [Suspend(by replacement user)], process target user of the restored node would be only the Suspend User.

  Even after the suspend is released, it remains as suspend user only.

  ・If the process before restoration is other than [Pull Back] or [Pull Back after Send Back], process target user of the restored node will become the one before replacement.

8.4.2.39. If PC version standard screen is used on iPad(Mobile Safari) or Android smart phone, attachment file cannot be downloaded.¶

• If PC version standard screen (GreyBox) is used on iPad(Mobile Safari) or Android smart phone, attachment file cannot be downloaded.

8.4.2.40. IM-Workflow does not support the operations on multiple browsers or multiple tabs, and does not support browser back.¶

• As are stated as limitations on intra-mart Accel Platform, IM-Workflow does not support the operations on multiple browsers or multiple tabs,

  and it does not support the browser back.

  
  

  Same user cannot operate multiple browsers or multiple tabs for the following reasons:

  
  

  ・Directory for the temporary upload of attachment file is for each user.

  ・User data IDs may overlap depending on the operations pattern.

  
  

  [*] This symptom occurs in the following operations patterns :

  a) Pattern 1

  ・Open the same temporary save screen from multiple browsers.

  ・Apply first from one browser.

  ・Temporary save later by one browser.

  
  

  b) Pattern 2

  ・Log in with the same user ID on different PCs.

  
  

  c) Pattern 3

  ・After the application is made from temporary save, transition to the temporary save screen by the browser back button and then apply.

  
  

  User data ID is provided as an item which can be arbitrarily set by customer applications.

  In order to assure the flexibility of design, association between User Data ID and the matter is not allowed for 1:N as well as for 1:1.

  As a consequence it is not possible for IM-Workflow from the business viewpoint

  to check if the overlap of user data IDs for the matter is caused by the invalid operations.

  
  

  In order to assure the uniqueness of user data ID, please check it by the action processes and others in the user program.

8.4.2.41. Matter Number Allocation Process (DB Sequence Version) is not available on SQLServer 2008.¶

• DB sequence function is not available on SQLServer 2008.

  Therefore, matter number allocation process (DB sequence version) provided by intramart Accel Platform 2013 Winter is not available.

8.4.2.42. Destination field of negotiation mail is displayed as [0 item] on iPad.¶

• When the PC version process screen is displayed on iPad - MobileSafari, destination field of negotiation mail will be shown as [0 item].

  This symptom is caused because of Safari specifications.

  However, it has been confirmed that the destination setting of negotiation mail and the mail transmission work correctly even though the mail destination field shows [0 item].

8.4.2.43. In case iOS8 is used, clicking the [x] icon on the screens such as History Reference, Flow Reference, and Confirmation User Status Confirmation Screen would not close the screens.¶

• In case iOS8 is used and if smart phone screens for IM-Workflow (history reference, flow reference, confirmation user status screen) are displayed on tabs, clicking the [x] icon on these screen would not cause the screens to close.

8.4.2.44. In case iOS8 is used and if screen such as History Reference, Flow Reference, and Confirmation User Status Confirmation Screen are opened from a separate tab on the Standard Process Screen, the standard process screen would turn black after leaving it for about 10 seconds.¶

• In case iOS8 is used and if screens (history reference, flow reference, confirmation user status screen etc.) are displayed on tabs from the standard process screen for IM-Workflow smart phones, standard process screen will turn black when the tab is closed after leaving the screen for about 10 seconds.

  Similar symptom would also occur on screens other than the standard process screen (such as the list screens).