<commit_before>[id='optimizer-domain-editor-con']
= Author planning assets with the {PLANNER} domain editor

{PLANNER} leverages the data modeller to create a domain model for constraint satisfaction problems.
//@doc-link: Domain models link?

In addition to its basic functionality (creating data objects and their properties), you can also use the *Data Objects* editor perspective in {CENTRAL} to enhance the data model with {PLANNER}-specific data object roles. The `Planning Entity` and `Planning Solution` roles are available in the {PLANNER} dock, accessed by clicking the image:optimizer-icon.png[{PLANNER icon}] on the right side of the *Data Objects* perspective.

These options are available in the {PLANNER} domain editor.

image::optimizer-data-object-dock.png[align="center"]

The content of the domain editor varies depending on the current selection:

* Selecting a data object displays settings defined on the data object level (https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#solutionClass[Planning Solution], https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntity[Planning Entity]).

* Selecting properties of the data object displays settings defined on the property level of the data object.

The overview of the {PLANNER} domain editor capabilities is shown in the following division:

*Data object level*

* None
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntity[Planning Entity] 
** xref:optimizer-difficulty-comparitor-proc[Configure a planning entity difficulty comparator]
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#solutionClass[Planning Solution]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#scoreOfASolution[Solution Score Type]

*Property level*

* None
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntity[Planning Entity]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningVariable[Planning Variable]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#valueRangeProviderOnPlanningEntity[valueRangeId]
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#solutionClass[Planning Solution]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#valueRangeProviderOnSolution[Planning Value Range Provider]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#valueRangeProviderOnSolution[Planning Value Range Provider id]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntitiesOfASolution[Planning Entity Collection]

<commit_msg>BXMSDOC-1996: resolving xref error<commit_after>[id='optimizer-domain-editor-con']
= Author planning assets with the {PLANNER} domain editor

{PLANNER} leverages the data modeller to create a domain model for constraint satisfaction problems.
//@doc-link: Domain models link?

In addition to its basic functionality (creating data objects and their properties), you can also use the *Data Objects* editor perspective in {CENTRAL} to enhance the data model with {PLANNER}-specific data object roles. The `Planning Entity` and `Planning Solution` roles are available in the {PLANNER} dock, accessed by clicking the image:optimizer-icon.png[{PLANNER icon}] on the right side of the *Data Objects* perspective.

These options are available in the {PLANNER} domain editor.

image::optimizer-data-object-dock.png[align="center"]

The content of the domain editor varies depending on the current selection:

* Selecting a data object displays settings defined on the data object level (https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#solutionClass[Planning Solution], https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntity[Planning Entity]).

* Selecting properties of the data object displays settings defined on the property level of the data object.

The overview of the {PLANNER} domain editor capabilities is shown in the following division:

*Data object level*

* None
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntity[Planning Entity] 
** xref:optimizer-difficulty-comparator-proc[Configure a planning entity difficulty comparator]
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#solutionClass[Planning Solution]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#scoreOfASolution[Solution Score Type]

*Property level*

* None
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntity[Planning Entity]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningVariable[Planning Variable]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#valueRangeProviderOnPlanningEntity[valueRangeId]
* https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#solutionClass[Planning Solution]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#valueRangeProviderOnSolution[Planning Value Range Provider]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#valueRangeProviderOnSolution[Planning Value Range Provider id]
** https://docs.jboss.org/optaplanner/release/latest/optaplanner-docs/html_single/index.html#planningEntitiesOfASolution[Planning Entity Collection]


{'fraction_non_alphanumeric': 0.10196078431372549, 'fraction_numerical': 0.0006820119352088661, 'mean_word_length': 6.434727503168568, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 24, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7492677', 'n_tokens_mistral': 1788, 'n_tokens_neox': 1727, 'n_words': 395}