M3CloudSlam

Understand · Field-Impact Available

Know what a setting does before you change it

A searchable catalogue of M3 fields and settings. For each one: what it does in plain words, where it acts in the process flow, and what it influences further on.

Field-ImpactAvailable
RLTDautomatic release

Delivery · field RLTD

Automatic release for picking

When enabled, M3 can release the delivery for picking automatically once the conditions are met.

Where it acts

Created›Allocated›Released for pickingacts here›Picked

Further on

The order type’s transaction type is copied onto the order, and decides again later in the flow.

Example field. Texts generated from the knowledge graph.

Why it matters

Today

  1. 1Search Infor documentation and forums
  2. 2Ask the one colleague, or a consultant, who knows
  3. 3Change it in a test environment and see what happens
  4. 4Hope nothing else depended on it

Settings stay untouched because nobody dares to change them.

With Field-Impact

  1. 1Search the field or setting by name
  2. 2Read what it does in plain words
  3. 3See where it acts, and what it influences further on

Know what a setting does before you change it.

How it works

From a field name to everything it touches

  1. 1 / 4

    Search any field or setting

    By its name or by what it is about, for example RLTD or automatic release.

    Field-ImpactAvailable
    RLTDautomatic release

    Example field. Texts generated from the knowledge graph.

  2. 2 / 4

    Read what it does

    In plain words, written from the user's side: what M3 does differently when it is on.

    Field-ImpactAvailable
    RLTDautomatic release

    Delivery · field RLTD

    Automatic release for picking

    When enabled, M3 can release the delivery for picking automatically once the conditions are met.

    Example field. Texts generated from the knowledge graph.

  3. 3 / 4

    See where it acts

    The step in the process flow where the setting makes the difference.

    Field-ImpactAvailable
    RLTDautomatic release

    Delivery · field RLTD

    Automatic release for picking

    When enabled, M3 can release the delivery for picking automatically once the conditions are met.

    Where it acts

    Created›Allocated›Released for pickingacts here›Picked

    Example field. Texts generated from the knowledge graph.

  4. 4 / 4

    Follow it further on

    Where its value is copied to another record and decides again, later in the flow.

    Field-ImpactAvailable
    RLTDautomatic release

    Delivery · field RLTD

    Automatic release for picking

    When enabled, M3 can release the delivery for picking automatically once the conditions are met.

    Where it acts

    Created›Allocated›Released for pickingacts here›Picked

    Further on

    The order type’s transaction type is copied onto the order, and decides again later in the flow.

    Example field. Texts generated from the knowledge graph.

On your own M3. Answers come from one knowledge graph of how M3 behaves, applied to your configuration and data. When something can’t be known, M3CloudSlam says so.

What it brings you

Change settings with confidence

  1. 1“You don’t need a consultant for that anymore”Your own key users and IT find out what a setting does, in seconds.
  2. 2No more trial and errorSee what a setting does before you try it in a test environment.
  3. 3No surprises further onKnow which later steps a change will also touch.
  4. 4Explained once, for goodThe explanation stays there for the next person who asks.

See Field-Impact on your own M3

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows