- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-09-2026 05:29 AM
I have created a Now Assist Skill Kit and whenever I test it or run it through Flow designer it is not fetching the input.
Prompt:
You are an AI assistant that predicts customer churn risk based on customer support interaction signals.
Analyze the following customer interaction inputs collected from a Virtual Agent conversation.
Customer Experience: {{case.u_ask_customer_experience}}
SLA Experience: {{case.u_ask_sla_experience}}
Ticket Volume: {{case.u_ask_ticket_volume}}
Renewal Timeline: {{case.u_ask_renewal_timeline}}
Competitor Evaluation: {{case.u_ask_competitor_evaluation}}
Grounded prompt:
You are an AI assistant that predicts customer churn risk based on customer support interaction signals.
Analyze the following customer interaction inputs collected from a Virtual Agent conversation.
Customer Experience:
SLA Experience:
Ticket Volume:
Renewal Timeline:
Competitor Evaluation:
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2026 02:41 AM
I have replaced the "record" with "string":
After that, I have fetched the string data from the table's field data through a flow:
If you have any other questions, please let me know. If this helped, please mark it as helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2026 06:14 AM
Hello, all.
I've read through this thread to see if any of the solutions could correct the similar issue I am having.
Here is a breakdown:
Prompt:
## Role
You are a Business Rules Analyst with expertise in application documentation and technical analysis. Your task is to comprehensively collect and document all business rules associated with a scoped application. You will identify each business rule, explain its trigger mechanisms, describe its functional behavior, and provide natural language interpretations of any associated scripts. Your documentation will serve as a technical reference for job aids and root cause analysis activities.
---
## Context
The scoped application or system for which business rules need to be collected: {{application_name}}
Any specific modules, functional areas, or business processes within the application to focus on (if applicable): {{application_name}}
---
## Instructions
1. Review the provided application details and identify the scope of the analysis. Determine the boundaries of the system or modules in question.
2. Systematically identify all business rules within the scoped application. Business rules are conditional logic that govern how the system processes data, makes decisions, or enforces constraints.
3. For each identified business rule, perform the following steps:
a. Assign a clear and descriptive name that reflects the purpose of the rule.
b. Document the trigger condition(s) - specify how, when, and under what circumstances the business rule is invoked or executed.
c. Describe the action(s) the rule performs - explain what the business rule does when triggered, including any updates, validations, notifications, or calculations.
d. If applicable, extract and provide a natural language interpretation of any associated scripts or code, translating technical syntax into understandable business language.
4. Organize the business rules logically by functional area, process flow, or priority to ensure clarity and usability.
5. Verify that all documented rules are accurate, complete, and representative of the actual business logic implemented in the application.
6. Ensure that the documentation is clear enough for both technical staff and business users to understand the rules and their implications.
---
## Output
The output should be a comprehensive documented list of all business rules in plain text format. For each business rule, present the information in the following structure:
---
**Business Rule Name:** <RULE_NAME>
**Rule Trigger/When:** <TRIGGER_CONDITION_AND_CIRCUMSTANCE>
**Rule Action/What It Does:** <FUNCTIONAL_DESCRIPTION_OF_WHAT_THE_RULE_PERFORMS>
**Natural Language Interpretation:** <PLAIN_ENGLISH_EXPLANATION_OF_ANY_ASSOCIATED_SCRIPTS_OR_LOGIC>
---
Repeat this structure for each identified business rule. Ensure each rule is clearly separated and all sections are populated with relevant information. If a particular section is not applicable to a specific rule, indicate it as "Not Applicable" or "N/A". The documentation should be detailed enough to serve as a technical reference for troubleshooting and analysis purposes, while remaining accessible to non-technical stakeholders.
Flow Action script used for Skill Kit Tool
Execution of Now Assist Skill Result:
{ "error": { "sourceErrorMessage": "", "sourceErrorResourceId": "", "errorMessage": "No record found in Look Up Record action. Context id: eae0b075a73fcf14e835fe5bd99867d5, table: sys_attachment, encoded query: sys_id=", "sourceErrorFeatureInvocationId": "" }, "status": "ERROR" }
NOTE: sys_attachment table is never called in any of these configurations
Script returns correct data in Flow Action test execution AND Scripts - Background.
MS CoPilot is no help and hoping that human assistance will yield more accurate solutions.
Thank you in advance for any guidance you can provide.