Showing posts with label crossover domain. Show all posts
Showing posts with label crossover domain. Show all posts

Tuesday, 6 December 2016

Automatically populate default user's Site on SR | IBM MAXIMO

1 create a Cross over domain
Domain: MAXUSER2SR
object: MAXUSER
Validation Where Clause: USERID = :user # (:USER means current logged in user)
Source Field: DEFSITE # (attribute in maxuser table)
Destination Field: SITEID

2 In Database Configuration; attach this domain (MAXUSER2SR) with attribute TICKETID in SR object

Saturday, 26 December 2015

Table Domain Vs Crossover Domain - IBM Maximo

Today one of my colleague has asked me the difference between Crossover domain and Table domain. He was confused and indeed he mixed up them both.
this is how I explained him.
First of all, as the names suggests, both have major differences in itself.  

Table Domain:

1.       It’s a list of value to show you all values in table
2.       We can populate only one field with one table domain.
3.       and yet, definitely we can re-use it as many times as we require.
4.       for Table domain, we don't need to know about the target application, can b use anywhere.
5.       table domains dynamically update its values, as they looked up table updates.
6.       for instance, in users’ application to create a new user. As we press lookup button, we see a list of persons’ table. And it updates automatically as the person’s records updates, insert, delete.

Crossover domain:

1.       It’s another type of domain to be use as lookup. It not only just lists us domain values but we can populate as many field as we require from source application to this (destination).
2.       for crossover, we must know target application and his field names to populates.
3.       Each field has to be mapped with source and target fields at the time of create a crossover domain.
4.       for example, we are creating a new user, when we select person from crossover domain, it populates other records as well automatically. We can use this to copy records/values from one application to another.
5.       We also can use relationship to drill child levels.