You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/09/15 13:06:00 UTC

[jira] [Commented] (SYNCOPE-1591) Support fetching data from internal storage for XML content loader

    [ https://issues.apache.org/jira/browse/SYNCOPE-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196127#comment-17196127 ] 

ASF subversion and git services commented on SYNCOPE-1591:
----------------------------------------------------------

Commit 96c9cd21efb951f8d27e54d41090467a2d075ffd in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=96c9cd2 ]

[SYNCOPE-1591] Introducing support for fetch statements, used by archetype to populate Flowable tables for test users


> Support fetching data from internal storage for XML content loader
> ------------------------------------------------------------------
>
>                 Key: SYNCOPE-1591
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1591
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.1.8, 3.0.0
>
>
> In some circumstances it could be useful to dynamically fetch data from internal storage while loading initial content, especially for statements that need to comply with referential integrity.
> Essentially, we need to extend the feature introduced by SYNCOPE-1498 by allowing to populate variables after SQL query execution.
> For example, the following entry:
> {code}
> <fetch key="procDef" query="SELECT ID_ FROM ACT_RE_PROCDEF WHERE KEY_='userWorkflow'"/>
> {code}
> will define a {{procDef}} variable whose result is obtained by executing the given query. In the following lines its value can be referenced via {{${procDef}}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)