Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. 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 Future consideration
Workspace Aspera Ideas
Created by Guest
Created on Sep 20, 2022

Provide a list of Custom Orchestrator Ruby Classes, and Read-Only Accessors for them

Through the WorkOrder custom class in a Custom Ruby module, you can access a list of work orders and their statuses and properties. I would like to have access to documentation on all of the custom ruby classes that enable interaction with Orchestrator, and also if possible to have read-only accessors for these classes (e.g. WorkOrderRO being a read-only accessor to WorkOrder) so that, for example, all running workflows can be listed and iterated over without the risk of accidentally assigning a new value to a property with an incorrectly written comparator (= instead of ==, for example).

Idea priority Medium
  • Guest
    Sep 21, 2022

    Example Ruby Code:
    outputs['WorkOrders'] = WorkOrder.find(:all, :conditions=>["status='In Progress'"])

    Produces this in outputs['WorkOrders']:

    [#<WorkOrder id: 464, name: "SQS_WATCHER_L1", workflow_id: 92, workflowName: "SQS_WATCHER_L1", comments: "", status: "In Progress", statusDetails: "Executing Step: Poll Queue for Messages (4497)", branchedFromOrder: nil, launched_by: 1, running_as: 2, workflow_revision_id: 9, initiatedBy: 1, branchedFrom: nil, forkedAt: nil, derivedFrom: nil, master_id: 464, created_at: "2022-09-15 15:00:31", updated_at: "2022-09-15 15:00:33", higherPriority: nil, initiate_date: "2022-09-15 15:00:32", completion_date: nil, priority: 2, max_running: 0, purge_after_days: nil, cleanup_after_days: nil, monitor_id: nil, tags: "|Sony|", label: "Sony - SQS Queue Watcher", exec_priority: 0.6666666666666666>]

    I have spoken with Christophe Thiebot from Orchestrator Professional Services about this if you would like more information from him - if the above is insufficient to proceed with this idea, please let me know what further information you require and I will endeavour to provide it.