Topics started by AdheeshaF

3 Topics

A
Do Gooder (Employee)
AdheeshaFDo Gooder (Employee)
posted in Assets (Asset Management)

Linking to pages with a tree navigator from GIS Map

Navigation can be enabled from the Object Information Dialog in the GIS Map page to tree navigators. To achieve this, the Page Name and Parameters must be defined in the GIS Object Configuration page as shown in the example below:Page Name: tree/EquipmentObjectStructureNavigation/EquipObjectStructureTreeParameters: MchCode=[#MCH_CODE]^Contract=[#CONTRACT] The Page Name, as shown below, can be easily created from the URL of the page the user should be navigated to. “tree/EquipmentObjectStructureNavigation/EquipObjectStructureTree”It is mandatory to begin the Page Name with “tree” The middle part contains the name of the client, which is EquipmentObjectStructureNavigation for the example provided above. The final part of the Page Name contains the tree view. It can be found in the URL of the page. For e.g.:  https://myserver.com/main/ifsapplications/web/page/EquipmentObjectStructureNavigation/EquipmentObjectPageF;$filter=EquipmentObjectSeq%20eq%2013;searchcontext=EquipmentObjectSeq:13,St

0
A
Do Gooder (Employee)
3 months ago
A
Do Gooder (Employee)
AdheeshaFDo Gooder (Employee)
asked in Assets (Asset Management)

Cannot delete serial object after status change

Once a Serial Object is created and its status is changed, its prevented from getting deleted due to having a historical row. Is there a particular functional reason for preventing the deletion of serial objects when it has more than one historical record? It can be deleted if its status has not been changed.

1
JerryB
Hero (Employee)
2 years ago
A
Do Gooder (Employee)
AdheeshaFDo Gooder (Employee)
asked in Document Management (DocMan)

Possibility of restricting the release of document revisions in random orders

Hi,Currently, document revisions can be released in any random order (irrespective of the order they were created). Would it cause problems if we put in some restrictions from that happening?Restrictions such as,1. We make sure that they can only be released in the order they were created in2. In a scenario where the value in the Update Revision field is set as “Latest Released Revision”, we keep the object connections in the latest created revision which was released without letting them move to a revision which was released after, but created much earlier?Thanks!

0
A
Do Gooder (Employee)
2 years ago

Badges

Show all badges
Terms & ConditionsCookie settings