Skip to main content
deleted 881 characters in body
Source Link
Alvin Reyes
  • 12.8k
  • 4
  • 23
  • 62

We have the ability to add, remove, and re-order items in a field per SDL Live Content(requires login).

Is there a way to get access to multiple fields in a component form from the same Custom URL pop-up?

Or would you recommend another high-level approach on setting up a "per-component" extensions. Requirements include:

  • External system(s) would provide select-able options to be saved in Tridion fields
  • Preference for simplifying the setup (avoid setting up a Custom URL per field)

The specific data doesn't matter, but may include configuration type content such asEdit:

  • List of non-Tridion items in a specific order
  • Filtering priority (e.g. "sort by X")
  • Identifiers to other systems (e.g. 1234, which represents another item)

These would be published and used in Content Delivery removed alternative ideas to drive some visitor functionality. Think tag library or control with some parameters.

I'm thinking a separate "tab" for the component form, an External Content Library approach (basically don't manage this in Tridion), and/or saving all the external "results" in a single Tridion field (or AppData) could also workmake question clearer. Anything else?

We have the ability to add, remove, and re-order items in a field per SDL Live Content(requires login).

Is there a way to get access to multiple fields in a component form from the same Custom URL pop-up?

Or would you recommend another high-level approach on setting up a "per-component" extensions. Requirements include:

  • External system(s) would provide select-able options to be saved in Tridion fields
  • Preference for simplifying the setup (avoid setting up a Custom URL per field)

The specific data doesn't matter, but may include configuration type content such as:

  • List of non-Tridion items in a specific order
  • Filtering priority (e.g. "sort by X")
  • Identifiers to other systems (e.g. 1234, which represents another item)

These would be published and used in Content Delivery to drive some visitor functionality. Think tag library or control with some parameters.

I'm thinking a separate "tab" for the component form, an External Content Library approach (basically don't manage this in Tridion), and/or saving all the external "results" in a single Tridion field (or AppData) could also work. Anything else?

We have the ability to add, remove, and re-order items in a field per SDL Live Content(requires login).

Is there a way to get access to multiple fields in a component form from the same Custom URL pop-up?

Edit: removed alternative ideas to make question clearer.

Source Link
Alvin Reyes
  • 12.8k
  • 4
  • 23
  • 62

How to handle multiple Tridion fields in a GUI extension?

We have the ability to add, remove, and re-order items in a field per SDL Live Content(requires login).

Is there a way to get access to multiple fields in a component form from the same Custom URL pop-up?

Or would you recommend another high-level approach on setting up a "per-component" extensions. Requirements include:

  • External system(s) would provide select-able options to be saved in Tridion fields
  • Preference for simplifying the setup (avoid setting up a Custom URL per field)

The specific data doesn't matter, but may include configuration type content such as:

  • List of non-Tridion items in a specific order
  • Filtering priority (e.g. "sort by X")
  • Identifiers to other systems (e.g. 1234, which represents another item)

These would be published and used in Content Delivery to drive some visitor functionality. Think tag library or control with some parameters.

I'm thinking a separate "tab" for the component form, an External Content Library approach (basically don't manage this in Tridion), and/or saving all the external "results" in a single Tridion field (or AppData) could also work. Anything else?