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 App Connect
Created by Guest
Created on Sep 9, 2024

Create function CURRENT_TIMESTAMP_NOW to return the current timestamp that is NOT the same within the node

CURRENT_TIMESTAMP is very helpful but always returns the same value within a node, by design.  This is useful, but there is a significant need to also capture the current timestamp as of a statement being executed for logging and monitoring and other reasons.  This is an extremely common problem, and the platform would benefit from a new function.  Even our IBM App Connect TAM has a common workaround for this and uses it on almost all his applications.

Examples:

  • We need to capture the response time of specific things like CREATE...DOMAIN.... or PASSTHRU

Workarounds:

  • Add a label & compute node to all applications.  The compute node should save CURRENT_TIMESTAMP to Environment.Variables.  When you need the timestamp, add 'PROPAGATE TO LABEL 'getTimeStamp' DELETE NONE;'
  • Do something similar with a java compute node.
  • Create a java function that returns the current timestamp.  When you need the timestamp, invoke the java function.

These workarounds add significant complexity and overhead to obtain a very simple data element.  Please add new function(s) that can simplify this common use case.

Idea priority High
  • Admin
    Ben Thompson
    Reply
    |
    Nov 29, 2024

    Thank you for taking the time to raise this enhancement request. We agree this would be a valuable addition to the product, and also agree that the workarounds all present a level of inconvenience that would be best avoided. Status is updated to Future Consideration.