Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Sep 30, 2021

Attributes defined as YORN data type should be allowed utilize crossover domains

While it is understandable that ALN, Numeric and Table Domains are not allowed to be defined on YORN datatype attributes in Maximo database configuration, there is a need for crossing YORN datatype attributes from one object to another. I have a business case where I need a YORN (checkbox field) on the item master to be copied to PR lines for PR lines of type ITEM, and be user populated for PR Lines of type MATERIAL. While researching how to handle this situation I also saw other cases of where YORN fields on Assets or locations needed to be crossed over to work orders.

I know this can be done with an automation script, but this seems like this is a straight forward use of cross over domains which are supported by IBM where automation scripts are considered customization and not supported by IBM.

Idea priority Medium
Needed By Quarter
  • Admin
    Kim Woodbury
    Reply
    |
    Oct 7, 2021

    Thank you for your submission. We do need more information as Steven has also commented, you would not trigger the crossover from the YORN but from another key value.

  • Guest
    Reply
    |
    Oct 4, 2021

    I'm not understanding the use case. Crossover domains are intended to set attributes on the record based on values in another object. For example, crossover ASSET data onto a WORKORDER. You tie the crossover domain to the attribute being set (such as ASSETNUM) that allows you to get the record (ASSET) to retrieve the other attributes to set (such as the CINUM out of the box). You do not tie the crossover domain to the attributes you want to set because the crossover domain will only fire when the attribute it is associated to is modified.

    You can set a YORN attribute via crossover but a YORN attribute wouldn't be the trigger so you wouldn't tie the crossover domain to the YORN attribute. In the example provided, the ITEMNUM would be where you associated the crossover domain with a validation where clause of itemnum = :itemnum and itemsetid = :itemsetid and you'd have that bring over your YORN attribute.