This is an IBM Automation portal for Cloud Management and AIOps 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Tool for use in converting of .txt file based scheduling object definitions to .json as payload in the REST requests.
Currently using TWS version and are leveraging TWS REST API to create a robust CI, CD workflow to deploy objects like JOBS, SCHEDULES, RESOURCES to TWS servers. At this point all the TWS objects definitions available in a .txt file using syntax mentioned here (https://www.ibm.com/docs/en/workload-automation/9.4.0?topic=objects-job-definition).
We are unable to use the .txt file based object definition as payload in the REST requests, we are manually converting the .txt based definition to .json to use in REST API based CD workflow.
Please help us with the below:
1) Options/tools from IBM to convert .txt based object definitions to .json.
2) Possibility to directly use the .txt based TWS object definition as payload in the REST request
Do not place IBM confidential, company confidential, or personal information into any field.