Hi EDG enthusiasts,
my understanding is, that a resource action (explore / modify) is executed
with the access rights / roles of the executing user (which is good).
Is there a way, to call a function from within the resource action script
that itself runs within another user context (basically
Hi EDG enthusiasts,
I try to factor out repetitive functions and constants into an included
script, to provide a single source of truth throughout the implementation.
I try to reuse the constants and functions in some explore- and modify
actions.
However, the results are mixed: not all function
ry 4, 2025 at 11:29:03 AM UTC+1 Bernd Johannes wrote:
> Hi Holger,
> many thanks for the quick reply - I assume 'workflow_1' is the ID / Tag of
> the workflow?
>
> Anyway - I have now the required pointer which I was missing:
> tbs.queryGraph() shall provide me with th
Hi everybody,
just to add our observation: at least in a mixed mode, where write and read
queries happen in parallel, we also see this kind of behavior, that the
system "seems" to serialize accesses in some way under certain
circumstances. I say "seems", as we can only judge from the blocking
b
eryGraph('workflow_1');
> graph.transaction(workflowGraph, 'Adding a triple', () => {
> owl.Thing.add(rdfs.seeAlso, owl.Nothing);
> });
>
> Which will create the added triple in the given workflow and record it
> properly in the change history.
>
> Does this gi
Hello everybody,
I struggle to find the right sequence of actions to select a workflow and
mutate data within via ADS.
I would appreciate a solution template, that documents the relevant steps.
The situation:
in ontology *M* there is a modify action bound to owl:Ontology that should:
- select o
