Skip to main content

Hi,

Can anyone help me with below query ? 

 

For Apps10, IFS introduced a new generic concept for Validity in basic data.  This enables the users to control whether a specific basic data code can be used or not, and can thus help in managing when a certain code is allowed.
E.g. if a code has been used, but should be discontinued, the old way of handling this has been to add something like DO NOT USE in the description, since it is not allowed to delete a code that is used.  This does however not prevent users from actually using it, and it will also present that text as part of description all places where that code has been used.  The new capability ensure that you can prevent the use of an old without having to do such actions.


In Document management, the new concept is not yet implemented, leaving an inconsistent application where the users do not have the above mentioned ability to control which basic data codes that should be allowed to use or not, which over time can cause problems.
This applies to:
Document Class, Formats, Media, Association Category, Approval Template, Document Milestone Template, Scale, Person Group, Document Archive, Document Archive Status, Reason For Issue, File Types, Document Type (at least).
Applying this concept also to these basic data will ensure a consistent solution.

 

Hence I would like to know from RnD, whether there is any plan to implement this feature in near future. If yes, the planned dates/release information and any other workaround that can be used.

 

Thanks and Best regards,

Thilini

Hi Thilini,

There is no Plan as such for the next release (21R2) for sure. But we could consider bringing this up as a candidate ina future release, with our product management. @JerryB @stpese 

 

Hi Thilini,

 

A possible workaround we have implemented for document class, not only for obsolete classes, but to control which classes can be used on which objects.  We’ve added a custom logical unit with the allowed connections (note field was used to see existing connections at the switch-on point and for future additions).

Custom Logical Unit

Then a custom event was created

Custom Event for Document Insertion

 

With an error message and stop on the Object Connection insertion

Event Action

 

This has worked reasonably well to curb the bad connections we don’t want (attaching certain things to customer order lines instead of header only for example).  In APPs (V9 UD13), it stops the connection and allows the user to select a different document class, it doesn’t tell them the right one, but does stop the wrong ones.  We are still using External CRM (V8), the event still works there, but the dialog and error is much less informative and just stops the connection.  The user must start again to get to the right one.

 

Regards,

Shawn

Hi,

In addition to the validity concept, there is also the generic concept of basic data translation.

Unfortuneately, this is not available in IFS document management solution. 

I would be really helpful to have that availabe in IFS DMS as well, especially if IFS is deployed as a global single instance in a corporate environment with people from different native languages.

regards

Johannes

Hi @Mayura Wasantha, @ShawnBerk , @JohannesWittwer ,

Thank you very much for all your comments.

Best Regards,

Thilini

Reply


Terms & ConditionsCookie settings