Hi gjz,
Good question — this is a very common challenge when moving from classic UI (UI Macro) to UI Builder / Workspace.
1. Key point (why you're stuck)
In UI Builder:
- You cannot directly call a Script Include like you do in UI Macros
- UI Builder works through Data Resources (APIs)
So your Script Include must be exposed via an API first
2. Recommended approach → Wrap Script Include in Scripted REST API (best practice)
This is the clean and supported way.
Step 1: Create Scripted REST API
- Go to: System Web Services → Scripted REST APIs
- Create a new API + Resource
Example:
(function process(/*RESTAPIRequest*/ request, /*RESTAPIResponse*/ response) {
var sctask = request.queryParams.sctask;
var ritm = request.queryParams.ritm;
var result = new MyScriptInclude().getConsolidatedNotes(sctask, ritm);
response.setBody(result);
})(request, response);
Step 2: Reuse your Script Include
Make sure your Script Include:
- Is Server-side
- Has a callable function
var MyScriptInclude = Class.create();
MyScriptInclude.prototype = {
getConsolidatedNotes: function(sctask, ritm) {
// your existing logic
}
};
3. Step 3: Create Data Resource in UI Builder
In UI Builder:
- Add Data Resource → REST API
- Configure:
- Method: GET
- Endpoint: your scripted API
Pass parameters like:
/api/x_your_scope/your_api? sctask=${state.sctask_sys_id}&ritm=${state.ritm_sys_id}
4. Passing parameters (important)
You were right — use:
✔ Client State Parameters
✔ OR Record fields (from form context)
Example:
@context.record.sys_id → SCTASK@context.record.request_item → RITM
5. Bind data to component
Once Data Resource is set:
- Bind response to:
- Data Table
- Text / List component
- Custom component
6. Alternative (not recommended)
You can use:
- GlideAjax (client script style)
But:
Not aligned with UI Builder architecture
Harder to maintain
7. Best practice
✔ Use Scripted REST API as wrapper
✔ Keep Script Include reusable (as you already have )
✔ Use Client State for dynamic params
