trench999

Re: Documentation for Form action types - Adobe Experience Manager Forms 15-10-2015

No. I am aware of how to setup form fields. I simply need to know what field names I need to use for creating a lead? No one knows? There is no documentation for this action type. That is this issues. Can all OOTB action type be documented please?

1.1K

Re: Documentation for Form action types - Adobe Experience Manager Forms 15-10-2015

I"m assuming Create Lead allows a publisher to quickly add a form to add a lead to a list. So, this requires form field setup. What fields and what property names, etc. There is no guide for this. Assume this is s marketing person creating a form. How do they setup the form to work properly?

1.1K

Re: Documentation for Form action types - Adobe Experience Manager Forms 15-10-2015

Let's start with Create Lead. We are trying to create subscriptions form for the email newsletters we run in CQ. If there is as better way then we can start with that.

1.1K

Re: Documentation for Form action types - Adobe Experience Manager Forms 15-10-2015

No, that is not what I meant. There are a bunch of OOTB actions with no documentation. Building custom actions is reasonably documented as you point out.

1.1K

Documentation for Form action types - Adobe Experience Manager Forms 15-10-2015

We are looking more closely at form action types and we're finding little to no documentation on these. For example, we want to quickly create a Campaign newsletter subscription form without coding. This should be action type = Create Lead. The action attributes requires a manual id be entered I assume. This should be populated by a list of lead lists at minimum. No documentation exists to tell us how to setup the fields in the form. If there is docs, can someone point us to them. If not, can we...

2.7K

Re: Node visibility limitation before activation - Adobe Experience Manager 15-10-2015

? We're talking about author visibility here. The only thing the news people will set is activation and deactivation. Will need more feedback to understand.

678

Re: Node visibility limitation before activation - Adobe Experience Manager 15-10-2015

No, by policy. Nodes will be in the tree that, by policy, must not be seen by other user groups. All of this "visibility" mgmt. is done by authors and can't be a CRX or useradmin task.

612

Re: Node visibility limitation before activation - Adobe Experience Manager 15-10-2015

Hi! I'll be more specific. News publishersCreate and activate news stories many times per dayOnce per week they create a story and and schedule the activation because the story has to be released at a certain time. No one can see the story other then the news team.Other dept publishersCreate news lists (fixed list style) from their own news stories and those from the news publishers; they need to see all activated news storiesThey cannot see or use unactivated news stories Is that better?

609

Node visibility limitation before activation - Adobe Experience Manager 15-10-2015

We have a case where we need to make a tree of nodes visible for fixed list inclusion by a variety of publishers. Some of these nodes in the tree must not be visible by these publishers. These special nodes are created on author and have a scheduled activation. How can we set read access based on activation of a node?

1.3K

Re: Wordpress integration - Adobe Experience Cloud 15-10-2015

Very easy. You can drop the DTM container code in your WordPress header.php and footer.php templates. Simply push all your scripts and tags to those sites from a central locations.

623

Likes given to

User

Count

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe