Pablo, Also, keep in mind that policies are inherited by child components (processors, process groups, etc), so you can enable viewing of Data Provenance for the whole flow for a given user by adding the user to the root group's "view the data" policy. Unless that policy is explicitly overridden for a child component, that user will be able to see data provenance for all components.
On Mon, Nov 21, 2016 at 6:07 PM Jeff <[email protected]> wrote: > Hi Pablo > > From the global policies menu, you can add the users that need to able to > query Data Provenance to the "query provenance" policy. > > For any component, such as the root group, or a particular processor, > you'll also want to add the user to "view the data" policies for the > respective components. > > On Mon, Nov 21, 2016 at 5:52 PM Pablo Lopez <[email protected]> > wrote: > > Ok. Thanks for that. > Would you know how can I enable this again? > > Pablo. > > On Tue, Nov 22, 2016 at 6:44 AM, Andrew Grande <[email protected]> wrote: > > Yes. > > It's a combination of a generic view data permission in the global menu > and specific access in the processing group. > > Andrew > > On Mon, Nov 21, 2016, 12:28 PM Pablo Lopez <[email protected]> > wrote: > > Hi, > > Any ideas as of why Data Provenance option is grayed out (not available) > and none of the processors show the option in the context menu? Is this > something to do with security? > > Thanks, > Pablo. > > > > > -- > Pablo Lopez. > Integration Architect > Integrado Pty Ltd > M: 044 84 52 479 > [email protected] > >
