OctaSapien

CPI Property Formatter

FREE
More actions

Found something we could improve?
Practical usage guide

Practical usage guide

A practical workflow for CPI Property Formatter

Convert SAP CPI key=value and Name: value lines into CPI properties, Groovy setProperty calls, Content Modifier TSV or ordered JSON in your browser.

1. Prepare

Paste the original content without manual cleanup so formatting problems remain visible and reproducible.

2. Review

Compare the formatted result with the source and confirm that only presentation changed, not values or semantics.

3. Apply

Validate the result against the interface contract and target CPI runtime before transporting or sharing it.

Verification before operational use

  • Use a representative case with the inputs needed to reproduce it.
  • Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
  • Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.

Where CPI Property Formatter fits in a delivery workflow

Best-fit use cases

Convert CPI property notes into properties, Groovy setProperty calls, Content Modifier TSV or ordered JSON. The first = or : separates a name from its value.

Representative example

Input on separate lines: CompanyCode=1000 and Region: AR. JSON output is an ordered array: [{"name":"CompanyCode","value":"1000"},{"name":"Region","value":"AR"}]. Inspect diagnostics for omitted or malformed lines.

What to verify next

Formatting runs in your browser. Formatting does not verify runtime semantics or deploy an iFlow. Check duplicate names, escaping and expected value types against the actual Content Modifier or script before use.