nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Method to set Default Page PreController

josephbreese

We have a perceived requirement to set some page level information upon design time. All components on the page will use this Page set data. With my limited TS/LS knowledge, I'm planning on using a Page PreController that sets a key in the RequestContext.PageScopeData Map. I'm concerned that upon design time a user will forget to insert the PreController or set values to an improperly named parameter. Is there a way to default this or a workflow to validate this?

I don't need a RTFM response I just need to know that it can be done easily (read: less than 2 days of programming for an average programmer who is not married to TS/LS) and I can sleep easy for the next few weeks until I need to cross that bridge or delegate.

Thanks

Find more posts tagged with

Comments

vpatel

Would a site level controller work for you? That way you dont have to do this for each and every page -- just do it once for your site and it'll execute on every page.

josephbreese

Well that would make sense except I left out some mundane details: the specs allow for a user to specify what languages a page supports. The site we are working on has ~1400 micro sites served up as individual pages under the main site. A micro site may cater to a specific demographic more than others so having more granular control at the page level is wanted. I'm not sure if we can assume complete translation at a microsite level. We assume English as a default but I'd like to have the English default provided to the code base (components and POJOs) via rules over assumtion and hard coding as default language may change for a German branded roll out, for example.

It's late and I'm typing gibberish. If anyone is fluent in "late night too much work on the mind", please post your thoughts. I'll post something more concrete in the morning.

AlexC

You can have a pre-site controller call the rules engine and then populate the RequestContext parameters with appropriate data from the results. RequestContext has a method to execute a rule which can be used inside a controller.

josephbreese

You can have a pre-site controller call the rules engine and then populate the RequestContext parameters with appropriate data from the results. RequestContext has a method to execute a rule which can be used inside a controller.

So how does this set a default page PreController? So far, the requirement is a page designer will build a page and they will set the available languages per page built, all components on the page will then display only those languages specified by the page.

An example would be a Press Release Component that has some content, one page may allow a French and Italian translation, another page will allow English and Spanish. The Component will have all 4 translations within it. So before any Component code is executed, I need a page level variable set by the page builder to specify the languages available. Another Component will render text links to switch between page set languages.

AlexC

This can be done by setting a page pre-controller for each page and as a parameter to you pre-controller set the language (so you can have a generic pre-controller written and controlled by parameters).

josephbreese

This can be done by setting a page pre-controller for each page and as a parameter to you pre-controller set the language (so you can have a generic pre-controller written and controlled by parameters).

I already know this and have it working. I would like to know if there is a way to check at Page design time that a MISSING & REQUIRED Page PreController is NOT set when the user attempts to save the page. IF the Page PreController is not specified, I want to "Do Something".

vpatel

I already know this and have it working. I would like to know if there is a way to check at Page design time that a MISSING & REQUIRED Page PreController is NOT set when the user attempts to save the page. IF the Page PreController is not specified, I want to "Do Something".

Check it at WF time?

Work_Order_Billing.rptdesign

josephbreese

Check it at WF time?

Forgive my ignorance as there is no Acronym map on the Forums, but what is WF, and can you give an example of using the "WF"?

Adam Stoller

Forgive my ignorance as there is no Acronym map on the Forums, but what is WF, and can you give an example of using the "WF"?

I'm not sure about the meat of the discussion - but "WF" generally means "Workflow" - as in the Publish LiveSite Content workflow, Submit workflow, etc.

I'll let someone else discuss how you can utilize some aspect of a workflow to do what you're looking for.