Clarifications

Clarifications provide information needed to continue project work. Answer in the item concerned so the response stays connected to its function, page or requested change.

Before you start — Open the item that asks the question and read its purpose. Prepare the missing decision, an example and any useful reference. Respond on that item so the rule and its outcome remain connected to the right work.

Find the question that needs your response

Find the question in its project context before answering similarly named items.

1. Open the task overview and inspect actions waiting for you.
2. Open the related business area, function, page, website or documentation item.
3. Click its answer action when a clarification is requested.
4. Read all questions before entering the response.

The question identifies information still missing from the requirement. The required behavior should be explained by your business context.

Answer a requirement question

Answer each requested point with the applicable rule and enough context to distinguish its outcomes.

1. Open Answer the clarifications for the item concerned.
2. Fill in Your answers with the requested information.
3. Describe one normal case and one exception when the rule allows several outcomes.
4. Add a supporting file when the form provides attachments.
5. Click Submit my answers.

The answers are recorded and the item can be reconsidered. Return to its detail to follow the updated state.

Answer a Studio question

Use the target page and original request when answering a question about a specific Studio change.

1. Open the submitted Studio request.
2. Click Answer the questions.
3. Read Clarification needed and answer each displayed question.
4. Add references when they help explain the result.
5. Click Send my answers and follow the request detail.

Studio continues evaluating the request with the additional information. Another question may be needed if the response still leaves the expected behavior ambiguous.

Make the answer testable

Describe reproducible situations, including the important exception that changes the result.

1. Identify who performs the action.
2. State the input and the business rule to apply.
3. Explain what should happen when the rule is met and when it is not.
4. Specify the result the user should see.

For example: “An approved customer can place an order. A pending customer sees an explanation and cannot confirm the order.”

Note — If no open question is shown, return to the item detail and read its current state. Answering a question supplies information; it does not by itself publish the final change.

Instead of “only valid customers can order”, explain what makes a customer valid, who decides it and what a pending customer sees. Specify whether that customer can save a draft, confirm an order or only read an explanation. The answer defines the rule; it does not itself create those behaviors.