<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://doc.stagesasaservice.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://doc.stagesasaservice.com/feed.php">
        <title>Stages Documentation - 261</title>
        <description></description>
        <link>https://doc.stagesasaservice.com/</link>
        <image rdf:resource="https://doc.stagesasaservice.com/_media/wiki/logo.png" />
       <dc:date>2026-04-30T00:08:17+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/admin_jobs?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ai_acknowledgements?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ai_configuration?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ai_privacy?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/api-tokens?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/assign_roles?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/assign?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/autologin_deployment_guide?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/autologin_system_design?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/autologin_system_requirements?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/autologin_windows_tools?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/change_password?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/chatbot_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/chatbot?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clearcase_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clearcase_migrating?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clearcase_operations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clearcase_profile?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clearcase_req?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clearcase?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/clickable_image?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_codebeamer?rev=1776089980&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_configuration?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_confluence_cloud?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_integrity?rev=1776089966&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_prefetch?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_profile?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_sharepoint_online?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/cms_subversion?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/collectionmigration?rev=1775678302&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/collector_data_rest_api?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/compare_process?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/compliance?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/config_ldap_sync?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/configure_browser?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/configure_font_for_process_visualization?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/configure_jaas_jgss?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/configure_stages?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/configure-languages?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/configure-search?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/consistency?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/copyprocess?rev=1777289751&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/create_reports?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reference_models?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_alternating_table?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_debug1?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_debug2?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_remove_tags?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_retrieving_element?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_retrieving_property?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_setting_data?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_switch?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_accessing_parameters?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_collecting_data?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_data?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_issues?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_msexcel?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_msproject?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_oldercontent?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_plaintext?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_attributes?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_comment_report?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_milestone_report?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_project_list?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_rolereport?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_subprojects?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_accessing_data?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_concepts?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_generalinfo_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_generalinfo_usecases?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_generalinfo?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_data_collector?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_reports_linked_script?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_reports?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started_customizing?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started_example?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started_installing_birt?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_getting_started?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_issues?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_configprop?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers_examples?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers_expression?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_dataset?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_globalvariables?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_poijava?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references_preloadedjava?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_references?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports_tipsandtricks?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custom_reports?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/customize_support_tile?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/custum_reports_generalinfo_architecture?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dashboard?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dependentelements?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/description_templates?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/descriptions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/diagnose_problems?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_cms?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_config_global?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_config_host_prop?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_config_host?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions_users?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/dimensions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/document_lifestyles?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/downloads?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/edit_tables?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_anchors?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_concepts?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_copypaste?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_directives?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_interface?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_links?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_migration?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_reference?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_references?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_resources?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_styles?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_tables?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/editor_unmanaged?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/element_abbreviations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/email_feedback?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/email_notification?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/enable_support?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/execution?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/fileaccess?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/files?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/generative_ai?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/guidance_cms?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/import_reference_model?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/import_reports?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/import-processes?rev=1777289911&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/install?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/instantiate?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/jira_feedback?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/kerberos_autologin?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/kerberos_faq?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_autocreation?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_basics?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_checklist?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_config_authenication?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_config_directories?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_ex_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_gen_info?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_getting_started?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_global_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_hints?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_key_attribute?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_language?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_log_information?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_mapping?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_ondemand?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_optional_attributes?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_overview?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_ssl?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_sync?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_testing?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_url_attribute?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_useful_info?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap_user_entries?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ldap?rev=1775670835&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/licenses?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/links?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/local_news?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/local_style_custom?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/lost_found?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/maintenance_mode?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/manage_process_participants?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/manage_process_release?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/manage_users_groups_permissions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/manage_workspaces?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/managed_service_setup?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/managefileaccess?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/managelandingpage?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/manageprocessversions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/mandatory_manual_upgrade_steps_for_version_74?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/mandatory_manual_upgrade_steps_for_version_75?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/mcpserver?rev=1776844055&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/metamodelstrategy?rev=1776704937&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/model?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/modeling-routine-process-parameters?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/modeling-routine-process?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/modeling?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/msproject?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/multi_factor_authentication?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/multilanguage?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/navigation?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/newprocesses?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/newworkspace?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ondemand_modules?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/options?rev=1777281908&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/overwrite?rev=1777457488&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/people_application?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/phase_freezes_concept?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/phase_freezes_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/phase_freezes_prepare?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/phase_freezes_usage?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/phase_freezes?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_architecture?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_archive?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_cleanup?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_execution_jira?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_execution_jiracloud?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_execution_rtc?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_execution?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_codebeamer?rev=1776089940&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_jira_tmp?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_jira?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_link?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_polarion?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_ptcilm?rev=1776089925&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_rtc?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_servicenow?rev=1776089903&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback_sharepoint_online?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_feedback?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_release_participant?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process_version_switch?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/process-import-troubleshooting?rev=1776771706&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/processexportinpdf?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/project_state?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_cms_profile_old?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_configuration_management?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_configuration_old?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_configuring_client?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_file_editing?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_general?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_integration_new?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_integration_old?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_member?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_new_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_new_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_new_profile?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_operations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_sandboxes?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_sessions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_source_integrity_client?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc_users?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/ptc?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/quicklinkvideos?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/release_details?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/releasenotes?rev=1776339692&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/releasenotesn?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/remoteassociations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/reports_predefined?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/reports_standard?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/reusedescriptions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_advanced?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_artifact_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_association_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_attribute_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_dataset?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_description?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_entity_name?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_link_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_metric_collection?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_metric_report?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_metric_result?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_process_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_process_element?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_project_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_request_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting_user_class?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/scripting?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/search_in_stages?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/search?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/security_settings?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/server.xml?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/setup_directory?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_columns?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_config_global?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_config_host_prop?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_config_host?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_links?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_ssl_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint_users?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sharepoint?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/smoke_test_suggestions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/sql_monitor?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/stages-permission-license-matrix?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/start_release_automation?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/start_sandbox?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/start?rev=1776769495&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_global_config?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_host_sections?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_host_specific?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_limitations?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_migration?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion_profile?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/subversion?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/system_requirements_mysql?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/system_requirements_oracle?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/system_requirements?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/tailor_process?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/tailor?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/tailoring_definition?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/tailoring?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/teams?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/understand?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_72_73?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_75?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_76?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_77?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_78?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_79?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_711?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_from_712?rev=1776861332&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_java?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_to_7_10_5?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/upgrade_troubleshooting?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/use_reports?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/usecopy?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/useprocessmodules?rev=1777291457&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/user_groups_permissions_scim?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/users_groups_permissions?rev=1776337486&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/versions?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/visualizations-troubleshooting?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/work_with_files?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/workspace_collections?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/workspaces?rev=1773421097&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.stagesasaservice.com/261/workwithfiles?rev=1773421097&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://doc.stagesasaservice.com/_media/wiki/logo.png">
        <title>Stages Documentation</title>
        <link>https://doc.stagesasaservice.com/</link>
        <url>https://doc.stagesasaservice.com/_media/wiki/logo.png</url>
    </image>
    <item rdf:about="https://doc.stagesasaservice.com/261/admin_jobs?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Administrative Jobs</title>
        <link>https://doc.stagesasaservice.com/261/admin_jobs?rev=1773421097&amp;do=diff</link>
        <description>Manage Administrative Jobs

Some administrative jobs should be executed on a regular basis. For that purpose, administrative jobs like role assignments or data exports can be run automatically.

Administrators can upload scripts via the Administration &gt; Jobs</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ai_acknowledgements?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages AI Acknowledgements</title>
        <link>https://doc.stagesasaservice.com/261/ai_acknowledgements?rev=1773421097&amp;do=diff</link>
        <description>Stages AI Acknowledgements

In order to use the AI features or the Stages Assistant, every user must accept the following acknowledgements:

“This feature uses an artificial intelligence language model. UL Solutions is not responsible for the content it produces, which may be incomplete, inaccurate or outdated.  This feature is not a substitute for advice from a qualified professional.  You are responsible for independently verifying the information that you obtain through this feature.”</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ai_configuration?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>AI Configuration</title>
        <link>https://doc.stagesasaservice.com/261/ai_configuration?rev=1773421097&amp;do=diff</link>
        <description>AI Configuration

AI Feature Configuration: Chatbot Assistant and Content Generation

Content generation must always be configured to use the AI features, while the chatbot itself is optional. However, if the chatbot is used, it requires content generation to be configured first.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ai_privacy?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages AI Data Privacy</title>
        <link>https://doc.stagesasaservice.com/261/ai_privacy?rev=1773421097&amp;do=diff</link>
        <description>Stages AI Data Privacy

Stages uses Microsoft Azure OpenAI services (Microsoft product name: Azure OpenAI in Foundry Models)  to implement AI-enabled features such as generating process content and the Stages AI Assistant. The following models are used by default:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/api-tokens?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>API-Tokens</title>
        <link>https://doc.stagesasaservice.com/261/api-tokens?rev=1773421097&amp;do=diff</link>
        <description>API-Tokens

For an external application to connect with Stages, it needs a way to authenticate itself. This can be done with API-tokens.

Server configuration / Setting the Token secret

Stages generates its API tokens on the basis of a unique secret that can only be set by the Stages administrator. This should be a random string value with at least 32 characters. This value should be stored in the file conf/secret.properties like this:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/assign_roles?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title></title>
        <link>https://doc.stagesasaservice.com/261/assign_roles?rev=1773421097&amp;do=diff</link>
        <description>wip</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/assign?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Assign roles</title>
        <link>https://doc.stagesasaservice.com/261/assign?rev=1773421097&amp;do=diff</link>
        <description>Assign roles

Assigning roles is important in a process for back-checking and viewing individual responsibilities. It is used in project- or program-specific processes, not for the metamodel.

To assign a role to a user:

	*  Go to the specific role in the workspace</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/autologin_deployment_guide?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Autologin Deployment Guide</title>
        <link>https://doc.stagesasaservice.com/261/autologin_deployment_guide?rev=1773421097&amp;do=diff</link>
        <description>Kerberos Autologin

Autologin Deployment Guide

Enable Support for Kerberos Autologin in Stages

Setup Active Directory

Configure JAAS and JGSS Support on the Stages Server

Configuring the Browser</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/autologin_system_design?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Autologin System Design</title>
        <link>https://doc.stagesasaservice.com/261/autologin_system_design?rev=1773421097&amp;do=diff</link>
        <description>Kerberos Autologin

Autologin System Design

The autologin mechanism implemented in Active Directory is based on the Kerberos standard. For HTTP authentication the SPNego token format (RFC4178) is used together with an extension to the HTTP protocol (RFC 4559).

Kerberos requires a KDC (Key Distribution Center), which is configured by the Active Directory Management Utilities. Each member of the Active Directory maintains a trust relationship to the KDC. For Windows Clients, it is the Computer A…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/autologin_system_requirements?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Autologin System Requirements</title>
        <link>https://doc.stagesasaservice.com/261/autologin_system_requirements?rev=1773421097&amp;do=diff</link>
        <description>Kerberos Autologin

Autologin System Requirements

Client PC

	*  The Client PC has to be a member of the Kerberos realm. Using Microsoft Active Directory, the name of the realm usually corresponds to the name of the Active Directory domain in capital letters. Example: if the company’s Active Directory domain name is “abc.com”, the name of the corresponding Kerberos realm is “ABC.COM”.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/autologin_windows_tools?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Windows Tools and Utilities</title>
        <link>https://doc.stagesasaservice.com/261/autologin_windows_tools?rev=1773421097&amp;do=diff</link>
        <description>Kerberos Autologin

Windows Tools and Utilities

The Windows Support Tools are located on every server installation CD, but with some versions of Windows they are not installed by default. Please search for a file named “suptools.msi” and install it. The installer package will depend on another file called “support.cab” inside the same directory.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/change_password?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to change the password</title>
        <link>https://doc.stagesasaservice.com/261/change_password?rev=1773421097&amp;do=diff</link>
        <description>How to change the password

To change your password, go to your user profile homepage, scroll down to Security and Privacy, and type your old as well as your new password. To make sure you are not mistyping the password and locking yourself out, you are asked for your new password twice.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/chatbot_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Assistant Configuration</title>
        <link>https://doc.stagesasaservice.com/261/chatbot_config?rev=1773421097&amp;do=diff</link>
        <description>Stages Assistant Configuration

The Stages Assistant is a chatbot that uses Generative AI to answer all kinds of questions using the process content defined in Stages.

You can find more on its basic usage and functionality here.

The sections below describe how to set up, train, and maintain the Stages Assistant.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/chatbot?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Assistant</title>
        <link>https://doc.stagesasaservice.com/261/chatbot?rev=1773421097&amp;do=diff</link>
        <description>Stages Assistant

The Stages Assistant is an AI-enabled chatbot that can answer a variety of questions about the processes managed in Stages.



To access the Stages Assistant, click the icon in the top right corner from anywhere in Stages.

The Assistant opens on the right side of the process content.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clearcase_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Configuration</title>
        <link>https://doc.stagesasaservice.com/261/clearcase_config?rev=1773421097&amp;do=diff</link>
        <description>ClearCase Integration

Stages Configuration


&lt;!—- **** Rational ClearCase Configuration **** --&gt;

&lt;cms-type name=&quot;ClearCase&quot; factory=&quot;de.methodpark.cms.clearcase.ClearCaseFactory&quot;&gt;

&lt;cms-property name=&quot;client&quot;
value=&quot;C:\Programme\Rational\ClearCase\bin\cleartool.exe&quot;/&gt;

&lt;!--**** Path for the location of snapshot views ****--&gt;
&lt;cms-property name=&quot;sandboxDirectory&quot; value=&quot;sandboxes/ClearCase&quot;/&gt;

&lt;!--**** Describes pattern for allowed file paths ****--&gt;
&lt;cms-property name=&quot;validatePath&quot;
value=&quot;^[^…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clearcase_migrating?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Migrating from Snapshot to Dynamic Views</title>
        <link>https://doc.stagesasaservice.com/261/clearcase_migrating?rev=1773421097&amp;do=diff</link>
        <description>ClearCase Integration

Migrating from Snapshot to Dynamic Views

The ClearCase integration of Stages has already been used with snapshot views (default) and you want to migrate to dynamic views.

Step 1:

Stop Stages Server

Step 2: 

Configure the properties required for usage of dynamic views in the ClearCase section of PKitConfig.xml:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clearcase_operations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ClearCase Operations and Commands</title>
        <link>https://doc.stagesasaservice.com/261/clearcase_operations?rev=1773421097&amp;do=diff</link>
        <description>ClearCase Integration

ClearCase Operations and Commands

Views

View Creation

	*  Snapshot View:
			*  mkview -snapshot [-vws &lt;view storage location&gt;] – tag 

&lt;view tag&gt; &lt;view location&gt;

	*  Dynamic View:
			*  mkview – tag &lt;view tag&gt; &lt;view storagelocation&gt;


View Deletion</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clearcase_profile?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creation of a CMS Profile in Stages</title>
        <link>https://doc.stagesasaservice.com/261/clearcase_profile?rev=1773421097&amp;do=diff</link>
        <description>ClearCase Integration

Creation of a CMS Profile in Stages

For details regarding the creation of a CMS profile in Stages please see the Stages User Guide.

The attributes of a ClearCase CMS profile are:

	*  Name: If you are using multiple CMS profiles within one Stages project, they can be distinguished by their name. (optional)</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clearcase_req?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>General Requirements and Information</title>
        <link>https://doc.stagesasaservice.com/261/clearcase_req?rev=1773421097&amp;do=diff</link>
        <description>ClearCase Integration

General Requirements and Information

	*  Supporting ClearCase Version 7 and 8.
	*  The ClearCase commandline client “cleartool.exe” and the “ClearCase Explorer” must be installed on the Stages Server (standard clientinstallation).
	*  The client must have access to the ClearCase server. Additionally access to all VOBs as well as View Storage Locations is required which should be accessible through Stages. The Stages service must be started with the user account that shall…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clearcase?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrate with ClearCase</title>
        <link>https://doc.stagesasaservice.com/261/clearcase?rev=1773421097&amp;do=diff</link>
        <description>Integrate with ClearCase

ClearCase Operations and Commands

General Requirements and Information

Stages Configuration

Creation of a CMS Profile in Stages

Migrating from Snapshot to Dynamic Views</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/clickable_image?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Adding Clickable Images in Description</title>
        <link>https://doc.stagesasaservice.com/261/clickable_image?rev=1773421097&amp;do=diff</link>
        <description>Adding Clickable Images in Description

Clickable images are typically needed in landing pages or when you want to provide a visual process map that can be clicked to take the user to a specific process element (like workflow, activity, guidance, etc.) in Stages or even an external weblink. Creating a clickable image involves two high-level steps:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_codebeamer?rev=1776089980&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-13T14:19:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Codebeamer</title>
        <link>https://doc.stagesasaservice.com/261/cms_codebeamer?rev=1776089980&amp;do=diff</link>
        <description>Codebeamer

not yet included in 26.1 - planned to be included in a future release

Stages supports Codebeamer tracker of type Document



Example Configurations

There are two modes how the adapter can be configured: “direct download” or “link to codebeamer”.
This mode defines what happens when the user clicks on Codebeamer file in Stages (download action).
The following sections show example configurations for each mode.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages CMS Configuration</title>
        <link>https://doc.stagesasaservice.com/261/cms_config?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

Stages CMS Configuration

The configuration of the SharePoint interface needs to be done in the cms section of Config.xml  (see example configuration below).


&lt;cms&gt;
 &lt;cms-type name=&quot;SharePoint&quot;
 factory=&quot;de.methodpark.cms.sharepoint.SharePointFactory&quot;&gt;
 &lt;cms-property name=&quot;http.authentication.hostname&quot; value=&quot;stages&quot;/&gt;
 &lt;cms-property name=&quot;stages.server.url&quot; value=&quot;http://stages/pkit&quot;/&gt;

 &lt;cms-host ident=&quot;sharepoint1&quot; name=&quot;http://myhost/sites&quot;
 displayName=&quot;Microsoft Sh…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_configuration?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>CMS Configuration</title>
        <link>https://doc.stagesasaservice.com/261/cms_configuration?rev=1773421097&amp;do=diff</link>
        <description>CMS Configuration

Stages can interact with configuration management systems to work with remotely stored files. The configuration for these systems is done in two simple steps:

	*  Add the xml snippet explained in this section to your Stages configuration for each configuration management system you want to work with</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_confluence_cloud?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Confluence Cloud</title>
        <link>https://doc.stagesasaservice.com/261/cms_confluence_cloud?rev=1773421097&amp;do=diff</link>
        <description>Confluence Cloud

You are able to connect Stages with Confluence Cloud. A typical URL looks like:

https://example.atlassian.net

Example Configuration (conf/config.xml):


&lt;cms-type name=&quot;confluencecloud&quot;&gt;
    &lt;cms-host ident=&quot;confluencecloud.ident.1&quot; name=&quot;https://example.atlassian.net&quot; displayName=&quot;Confluence Cloud Example&quot;&gt;
        &lt;cms-property name=&quot;user&quot; value=&quot;user@example.com&quot;/&gt;
        &lt;cms-property name=&quot;password&quot; value=&quot;ATATT3xxxxxxxxxxx&quot;/&gt;
	&lt;cms-property name=&quot;spacekey&quot; value=&quot;SPACE…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_integrity?rev=1776089966&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-13T14:19:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrity</title>
        <link>https://doc.stagesasaservice.com/261/cms_integrity?rev=1776089966&amp;do=diff</link>
        <description>Integrity

not yet included in 26.1 - planned to be included in a future release

Example Configuration (conf/config.xml):


&lt;cms-type name=&quot;integrity&quot;&gt;
    &lt;cms-host ident=&quot;integrity.ident.1&quot; name=&quot;integrity.myserver.com&quot; displayName=&quot;Test Integrity Server&quot;&gt;
        &lt;cms-property name=&quot;protocol&quot; value=&quot;http&quot; /&gt;
        &lt;cms-property name=&quot;port&quot; value=&quot;7001&quot; /&gt;
        &lt;cms-property name=&quot;user&quot; value=&quot;integrity_username&quot; /&gt;
        &lt;cms-property name=&quot;password&quot; value=&quot;integrity_password&quot; /&gt;
    …</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_prefetch?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>CMS Prefetch Configuration</title>
        <link>https://doc.stagesasaservice.com/261/cms_prefetch?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

CMS Prefetch Configuration

The CMS prefetch is a Stages system service. It ensures that Stages displays up to date information of documents that are managed by an external configuration management system (CMS). Therefore the CMS prefetch is scheduled periodically to retrieve the latest revision information for all documents of active projects.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_profile?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create a New CMS Profile</title>
        <link>https://doc.stagesasaservice.com/261/cms_profile?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

Create a New CMS Profile

	*  Entering a Name for a CMS profile is optional. When a name is specified it will be displayed in forms where a document/file is associated with a CMS profile.
	*  It is required to select a SharePoint Host (corresponds to a cms-host as defined in Config.xml).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_sharepoint_online?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Sharepoint Online</title>
        <link>https://doc.stagesasaservice.com/261/cms_sharepoint_online?rev=1773421097&amp;do=diff</link>
        <description>Back to CMS Configuration

Sharepoint Online

You are able to connect Stages with SharePoint Online. A typical URL to SharePoint Online looks like:

https://companyname.sharepoint.com/

Example Configuration


&lt;cms-type name=&quot;sharepointonlinegraph&quot;&gt;
    &lt;!-- Global Properties --&gt;
    &lt;cms-host ident=&quot;sharepoint.online.ident&quot; name=&quot;https://example.sharepoint.com&quot; displayName=&quot;SharePoint Online Example&quot;&gt;
        &lt;!-- Host Properties --&gt;
        &lt;cms-property name=&quot;client.id&quot; value=&quot;xxxx-xxxx-xxxx-…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/cms_subversion?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Subversion</title>
        <link>https://doc.stagesasaservice.com/261/cms_subversion?rev=1773421097&amp;do=diff</link>
        <description>Back to CMS Configuration

Subversion

Stages supports SVN 1.9, 1.10 and 1.14

Example Configuration


&lt;cms-type name=&quot;subversion&quot;&gt;
    &lt;!-- Global Properties --&gt;
    &lt;cms-host ident=&quot;subversion.example.ident&quot; name=&quot;https://subversion.example.net:1234&quot; displayName=&quot;Subversion Example Server&quot;&gt;
        &lt;!-- Host Properties --&gt;
        &lt;cms-property name=&quot;user&quot; value=&quot;subversion_username&quot; /&gt;
        &lt;cms-property name=&quot;password&quot; value=&quot;subversion_password&quot; /&gt;
    &lt;/cms-host&gt;
&lt;/cms-type&gt;</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/collectionmigration?rev=1775678302&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-08T19:58:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Migrate process interface handling</title>
        <link>https://doc.stagesasaservice.com/261/collectionmigration?rev=1775678302&amp;do=diff</link>
        <description>Migrate process interface handling

If you have used workspace groups to control process interfaces, you need to create workspace collections to group the workspaces that should continue to have interfaces between each other.

Examples are

	*  all modelling workspaces that will be integrated into standard process workspaces</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/collector_data_rest_api?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Collector Data REST API</title>
        <link>https://doc.stagesasaservice.com/261/collector_data_rest_api?rev=1773421097&amp;do=diff</link>
        <description>Collector Data REST API

The REST API feature provides a framework to create customized REST API endpoints each designed to serve a specific use case. This allows to extract structured information (JSON) from Stages for usage in external systems in a flexible, secure and easy-to-use way.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/compare_process?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Compare Processes</title>
        <link>https://doc.stagesasaservice.com/261/compare_process?rev=1773421097&amp;do=diff</link>
        <description>Compare Processes

Stages allow users to compare different processes directly in the tool easily. Comparison can be started on the Process main page via the Compare menu.

&lt;https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=659230&amp;media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/compare.png&gt;

Watch this video to see how the process comparison works:

You can compare different versions of one process and different processes, e.g., two process variants. B…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/compliance?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Compliance</title>
        <link>https://doc.stagesasaservice.com/261/compliance?rev=1773421097&amp;do=diff</link>
        <description>Manage Compliance

Development of complex products is always a regulated environment. Examples are standards set by governing bodies like the FAA or FDA, ISO or IEEE standards, quality, safety, security, environmental, or health standards, or market requirements like Automotive SPICE. Managing compliance with all relevant standards is a key aspect of process management.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/config_ldap_sync?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>LDAP Synchronization</title>
        <link>https://doc.stagesasaservice.com/261/config_ldap_sync?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

LDAP Synchronization

The Stages user database can be synchronized with various LDAP directory servers (e.g. OpenLDAP, Windows Active Directory). This allows password sharing among different systems. Detailed information about LDAP synchronization can be found in the Stages</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/configure_browser?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring the Browser</title>
        <link>https://doc.stagesasaservice.com/261/configure_browser?rev=1773421097&amp;do=diff</link>
        <description>Deployment Guide

Configuring the Browser

To use the autologin feature, a browser has to be configured to use SPNego authentication for trusted Intranet sites. Furthermore proxy usage for Intranet sites should be disabled.

Firefox

Open the Firefox configuration page by typing</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/configure_font_for_process_visualization?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title></title>
        <link>https://doc.stagesasaservice.com/261/configure_font_for_process_visualization?rev=1773421097&amp;do=diff</link>
        <description>*  Place the font file in the folder conf/fonts
	*  Add the diagram.font property to your config.xml file in the following way: 
&lt;property name=“diagram.font” value=“Pacifico:Pacifico-Regular.ttf”/&gt;
	*  Make sure your scriptconfig.js of the metamodel contains the following code line:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/configure_jaas_jgss?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configure JAAS and JGSS Support on the Stages Server</title>
        <link>https://doc.stagesasaservice.com/261/configure_jaas_jgss?rev=1773421097&amp;do=diff</link>
        <description>Deployment Guide

Configure JAAS and JGSS Support on the Stages Server

Java Authentication and Authorization Service (JAAS)

JAAS is a standard Java API, which has to be configured with your network settings. Please edit the provided example file conf/jaas.conf and replace the example values according to your network configuration:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/configure_stages?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configure the Stages server</title>
        <link>https://doc.stagesasaservice.com/261/configure_stages?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages server

Stages installation location

The Stages installation location is referenced in this document as &lt;STAGES_HOME&gt; or $STAGES_ROOT which is the environment variable used by Stages to determine its base directory. The default location for</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/configure-languages?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configure additional languages</title>
        <link>https://doc.stagesasaservice.com/261/configure-languages?rev=1773421097&amp;do=diff</link>
        <description>Configure additional languages

Stages comes with English, German and Chinese translations. Other languages can be added in the following way:

	*  Edit conf/config.xml and add/edit the following property by adding the additional language, e.g. “ja</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/configure-search?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Multi language search indexing</title>
        <link>https://doc.stagesasaservice.com/261/configure-search?rev=1773421097&amp;do=diff</link>
        <description>Multi language search indexing

Attention! The file “element-mapping.json” gets overwritten on Stages updates. Create a backup copy if you want to save your work.

For multi language support the following steps have to be executed:

1. Stop Stages and Stages Search</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/consistency?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Check Process Consistency</title>
        <link>https://doc.stagesasaservice.com/261/consistency?rev=1773421097&amp;do=diff</link>
        <description>Check Process Consistency

Process consistency is especially important when creating new processes.

To perform consistency checks, go to Management &gt; Process Versions and choose the Check Readiness operation from the context menu for the Working Version. These checks also run automatically when you click Add version to create a new process version.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/copyprocess?rev=1777289751&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-27T11:35:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Copy a Process</title>
        <link>https://doc.stagesasaservice.com/261/copyprocess?rev=1777289751&amp;do=diff</link>
        <description>Copy a Process

A predefined process can be imported into another workspace using Copy process.

1. Create the workspace where the process has to be imported.

2. Next navigate to the Process tab in that workspace and select the Copy process function.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/create_reports?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create reports</title>
        <link>https://doc.stagesasaservice.com/261/create_reports?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Create reports

Reports are ...

TBD</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reference_models?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create Custom Reference Models</title>
        <link>https://doc.stagesasaservice.com/261/custom_reference_models?rev=1773421097&amp;do=diff</link>
        <description>Create Custom Reference Models

Reference Models

Reference models are very similar normal Stages process, but typically use a different metamodel to define compliance requirements. Typically, a metamodel called TTO-Model for Standards (or similar) is already installed on every server, which is equipped to model Chapters and Requirements.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_alternating_table?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Alternating Table Row Color</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_alternating_table?rev=1773421097&amp;do=diff</link>
        <description>Alternating Table Row Color

Instructions

	*  Click on the table from the outline view.
	*  Then on the properties editor, click the Highlight tab.
	*  Click Add. (You will see three drop downs)
			*  Just type row._rownum%2 in the first drop down.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_debug1?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Debugging of BIRT Scripts (File Based)</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_debug1?rev=1773421097&amp;do=diff</link>
        <description>Debugging of BIRT Scripts (File Based)

This kind of debugging works under the following conditions:
SystemLimitationsReport preview in the BIRT DesignerThe debugging results/files are accessible on the local computer.Report runs on Stages ServerThe debugging results/files are accessible only on the Stages server.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_debug2?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Debugging of Data Set Scripts (Dataset Based)</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_debug2?rev=1773421097&amp;do=diff</link>
        <description>Debugging of Data Set Scripts (Dataset Based)

The following debugging mechanism can be used for Data Set scripts and Data collector scripts even if no Stages Server command line access is available.

Instructions

1. Add a results column with the name &#039;debug&#039; to your Data Set</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_remove_tags?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Remove HTML Tags from Stages Element Descriptions within the Data Set Script</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_remove_tags?rev=1773421097&amp;do=diff</link>
        <description>Remove HTML Tags from Stages Element Descriptions within the Data Set Script

The following function can be used for Data Set scripts and will remove all HTML tags.

Instructions

1. Add the following javascript function to your Data Set script.


function stripHTML(str){
 var s=new String(str);
 var re= /&lt;\S[^&gt;&lt;]*&gt;/g
 return s.replace(re, &quot;&quot;)
}</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_retrieving_element?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Retrieving the Parent Element Path</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_retrieving_element?rev=1773421097&amp;do=diff</link>
        <description>Retrieving the Parent Element Path

Function to Retrieve the Parent Element Path


function getParent(myelement) {
 var path = &quot;&quot;;
 do {
 var parent =

 myelement.getEntities(&quot;hierarchy::HIERARCHIC@LOCAL,targetrole=parent&quot;);

 if (parent[0].getProperty(&quot;IndexMode&quot;) == 1) {
 return (path);
 }
 if (path ==&quot;&quot;)
 path = parent[0].getProperty(&quot;DisplayName&quot;);
 else
 path = parent[0].getProperty(&quot;DisplayName&quot;) + &quot; | &quot;+path;
 myelement = parent[0];
 } while (parent[0].getProperty(&quot;IndexMode&quot;) != 1);
 ret…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_retrieving_property?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Retrieving Property Key Values</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_retrieving_property?rev=1773421097&amp;do=diff</link>
        <description>Retrieving Property Key Values

This example shows how to retrieve the localization property message keys from Stages.


properties_en = new Properties();
properties_de = new Properties();
stream_en = new FileInputStream(&quot;tomcat/webapps/pkit/WEB-INF/classes/
LocalPKit.properties&quot;);
stream_de = new FileInputStream(&quot;tomcat/webapps/pkit/WEB-INF/classes/
LocalPKit_de.properties&quot;);
properties_en.load(stream_en);
properties_de.load(stream_de);
stream_de.close();
stream_en.close();

/* Retrieve message…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_setting_data?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Setting Data Source Login Credentials with XML File</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_setting_data?rev=1773421097&amp;do=diff</link>
        <description>Setting Data Source Login Credentials with XML File

To configure the Stages Data Source credentials like server url, user name and password it is recommended to use the following XML based method.

Instructions

1. Create an XML file with the name PkitMetrics.xml with the following content:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_switch?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Switch Context to Viewing User</title>
        <link>https://doc.stagesasaservice.com/261/custom_report_tipsandtricks_switch?rev=1773421097&amp;do=diff</link>
        <description>Switch Context to Viewing User

Each dataset script is executed by default with the datasource user. That means that the report is fixed to one user regardless of the user who is executing the report in Stages. With the asCurrentUser.run() method, it is possible to switch the context to the viewing user (the user who is executing the report in Stages).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_accessing_parameters?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Accessing Report Parameter through a Data Set Script</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_accessing_parameters?rev=1773421097&amp;do=diff</link>
        <description>Accessing Report Parameter through a Data Set Script

This example shows how to pass a report paramter to a Stages Data Set collection script.

1. Create a Report with a Stages Data Source and a Data Set

2. Create the following Data Set result columns:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_collecting_data?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Collecting External Data</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_collecting_data?rev=1773421097&amp;do=diff</link>
        <description>Collecting External Data

Connecting a JDBC Database via Stages Data Source

The Java Database Connectivity (JDBC) API provides universal data access from the Java programming language. Using the JDBC 3.0 API, you can access virtually any data source, from relational databases to spreadsheets and flat files. JDBC technology also provides a common base on which tools and alternate interfaces can be built.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_data?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading Data Collector Results</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_data?rev=1773421097&amp;do=diff</link>
        <description>Reading Data Collector Results

To read the results that a data collector has written into the metric database, you can use the javascript funtion &#039;GetMetricResults&#039;.

Prerequisites:

	*  An existing Data Collector
	*  The Data Collector has collected some valid data.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_issues?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading Issues from Stages</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_issues?rev=1773421097&amp;do=diff</link>
        <description>Reading Issues from Stages

This example reads all issues from the current project and returns a given number of columns.

1. Create a Report with a Stages Data Source and a Data Set.

2. Create the following Data Set result columns:
NameType#idString</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_msexcel?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading MS Excel Files</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_msexcel?rev=1773421097&amp;do=diff</link>
        <description>Reading MS Excel Files

The used Java library POI Version 3.8 is able to read MS Excel files up to Version 2010.

1. Create a Report with a Stages Data Source

2. Create an Artifact and create and Artifact Instance (File) in Stages by uploading a MS Excel file.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_msproject?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading MS Project Files</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_msproject?rev=1773421097&amp;do=diff</link>
        <description>Reading MS Project Files

The used Java library MPXJ Version 4.3 is able to read MS Project files up to Version 2010.

1. Create a Report with a Stages Data Source

2. Create an Artifact and create an Artifact Instance (File) in Stages by uploading a MS Project file.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_oldercontent?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Accessing Older File Version Content</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_oldercontent?rev=1773421097&amp;do=diff</link>
        <description>Accessing Older File Version Content

1. Use the report example from the MS Excel Example Report

2. Create a new version of the Artifact Instance (File) in Stages by uploading a changed MS Excel file.

3. Update the Data Set with 2 additional result columns:
NameTypeAInteger</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_plaintext?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading Plain Text Files</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_plaintext?rev=1773421097&amp;do=diff</link>
        <description>Reading Plain Text Files

This example shows how to read data out of a CSV file which is controlled by Stages through a configuration management system.

1. Create a Report with a Stages Data Source and a Data Set

2. Create the following Data Set result columns:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_attributes?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading Attributes</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_attributes?rev=1773421097&amp;do=diff</link>
        <description>Reading Attributes

Stages allows to configure attributes in the metamodel.

Assume that the following attribute types are configured in your PKitConfig.xml file:


 &lt;attributeTypes&gt;
 &lt;attributeType ident=&quot;important_type&quot; type=&quot;BOOLEAN&quot; /&gt;
 &lt;attributeType ident=&quot;identifier_type&quot; type=&quot;STRING&quot; /&gt;
 &lt;attributeType ident=&quot;phaseState&quot; type=&quot;SELECTION&quot;&gt;
   &lt;option ident=&quot;future&quot; defaultOption=&quot;true&quot;/&gt;
   &lt;option ident=&quot;active&quot;/&gt;
   &lt;option ident=&quot;completed&quot;/&gt;
   &lt;/attributeType&gt;
 &lt;/attributeTypes&gt;</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_comment_report?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating an Annotation/Comment Report</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_comment_report?rev=1773421097&amp;do=diff</link>
        <description>Creating an Annotation/Comment Report

This example reads all annotations from all sub workspaces of the current one.

1. Create a report with a Stages Data Source and a Data Set.

2. Create the following Data Set result columns:
NameTypeProjectString</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_milestone_report?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating a Milestone Report</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_milestone_report?rev=1773421097&amp;do=diff</link>
        <description>Creating a Milestone Report

This example creates a milestone overview report which shows all assigned documents of a milestone together with the document state and document version.

1. Create a Report with a Stages Data Source and a Data Set

2. Create the following Data Set result columns</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_project_list?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating a Project List</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_project_list?rev=1773421097&amp;do=diff</link>
        <description>Creating a Project List

This Data Set script creates a list of all available projects in Stages and returns the Project ID and the full path of the project.


saveColumn(pkit.getRootProject());
getChilds(pkit.getRootProject());
function getChilds(project){
 var myprojects =
 project.getEntities(&quot;hierarchy::hierarchic@LOCAL,targetrole=children&quot;);
 for (var i=0;i&lt;myprojects.length;i++){
 saveColumn(myprojects[i]);
 getChilds(myprojects[i]);
 }
}
function projectparent(project) {
 var myprojects =…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_rolereport?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating a Role Report</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_rolereport?rev=1773421097&amp;do=diff</link>
        <description>Creating a Role Report

This example shows how to collect all roles in a process and their assigned users.

1. Create a Report with a Stages Data Source and a Data Set

2. Create the following Data Set result columns:
NameTypeUsernameStringFullnameString</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_subprojects?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading Subprojects</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process_subprojects?rev=1773421097&amp;do=diff</link>
        <description>Reading Subprojects

This example shows how to collect data from all projects (or all subprojects).

1. Create a report with a Stages Data Source and a Data Set.

2. Copy the Data Set script from the example into your Data Set.


/* Iterate through all projects */
getChilds(pkit.getRootProject());
/* Iterate through all subprojects */
//getChilds(pkit.getCurrentProject());
function getChilds(project)
{
 var myprojects =
 project.getEntities(&quot;hierarchy::hierarchic@LOCAL,targetrole=children&quot;);
 fo…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading Process Information</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading_process?rev=1773421097&amp;do=diff</link>
        <description>Reading Process Information

Creating a Role Report

Creating a Milestone Report

Creating an Annotation/Comment Report

Reading Attributes

Reading Subprojects

Creating a Project List</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reading File Content from a Stages CMS Profile</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data_reading?rev=1773421097&amp;do=diff</link>
        <description>Reading File Content from a Stages CMS Profile

Reading MS Excel Files

Reading Plain Text Files

Reading MS Project Files

Accessing Older File Version Content</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_accessing_data?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Accessing Data</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_accessing_data?rev=1773421097&amp;do=diff</link>
        <description>Accessing Data

Reading File Content from a Stages CMS Profile

Reading Process Information

Reading Issues from Stages

Collecting External Data

Accessing Report Parameter through a Data Set Script</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_concepts?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Concepts</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_concepts?rev=1773421097&amp;do=diff</link>
        <description>Concepts

Current Metric

The current metri is a preview paramter for the Stages Data Set.

For some function like pkit.getCurrentProject or some global variables like currentMetric the BIRT Designer need a preview location in the Stages Server.

Note: The current metric is only used by the BIRT Designer and not by the Stages server.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_generalinfo_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Limitations</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_generalinfo_limitations?rev=1773421097&amp;do=diff</link>
        <description>Limitations

This page describes the limitations of the Stages BIRT Designer compared to the Standard BIRT Designer.

Drill Down

Drill Down functionality from BIRT through separate reports is not supported by Stages.

Notice: The root cause is that the Report design files (*.rptdesign) are stored in the process database and there is no</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_generalinfo_usecases?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Cases</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_generalinfo_usecases?rev=1773421097&amp;do=diff</link>
        <description>Use Cases
Data SourceTrend Information NeededDescriptionXML, Web Service, Flat file, JDBC databasesNO   
This is standard BIRT functionality. Please refer to the book “BIRT: A field Guide to Reporting” for more information. 
  
Note: Make sure that the server is running Stages can access the Data Sources from an IT point of view.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_generalinfo?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>General Information</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_generalinfo?rev=1773421097&amp;do=diff</link>
        <description>General Information

Stages Supports metrics and report by integrating the BIRT system (BIRT is an open source Eclipe-based reporting system that integrates your Java/J2EE application to produce reports, see http://www.eclipse.org/birt/).

This guide describes the enhancements and additional plug-ins which will be delivered from us. Please refer to the following sources for BIRT specific information.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_data_collector?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating Stages Data Collector</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_data_collector?rev=1773421097&amp;do=diff</link>
        <description>Creating Stages Data Collector

Create a Data Collector

	*  Log into Stages as a user different to the superuser (administrator).
			*  The user needs at least (RMC) permissions of the domain Reports and Data Collectors.
			*  Note: Otherwise you cannot get the Data Collector running because the Data Collector is running in the context of the user who saved the collector the last time. For security reasons, the superuser context is disabled.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_reports_linked_script?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title></title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_reports_linked_script?rev=1773421097&amp;do=diff</link>
        <description>importPackage( Packages.javax.xml.parsers);
importPackage( Packages.org.xml.sax);
importPackage( Packages.org.w3c.dom);
importPackage( Packages.java.io);
function load_document(file) {
factory = DocumentBuilderFactory.newInstance();
builder = factory.newDocumentBuilder();
filestream = new FileInputStream( file );
document = builder.parse( new InputSource( filestream ));
filestream.close();
return document;
}
function getTagValue(document, tagName) {
nlist = document.getElementsByTagName(tagName)…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_reports?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating Stages BIRT Reports: A Basic Example</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started_creating_reports?rev=1773421097&amp;do=diff</link>
        <description>Creating Stages BIRT Reports: A Basic Example

This section explains how to create a basic BIRT report that extracts information from Stages.

Create a Report

	*  The BIRT RCP Designer is started by executing the birt.exe
	*  Select File –&gt; New –&gt; New Report</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started_customizing?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Customizing of the PkitMetrics.xml</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started_customizing?rev=1773421097&amp;do=diff</link>
        <description>Customizing of the PkitMetrics.xml

The PkitMetrics.xml comes with the Stages Installation (v.6 and higher) and is stored in the following directory:

[Stages directory]\conf\metrics.xml

In order to customize it, proceed with the following steps:

	*</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started_example?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Example for a Dataset Script</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started_example?rev=1773421097&amp;do=diff</link>
        <description>Example for a Dataset Script

This example illustrates how the Staes Javascript API is working.


var artifacts =
 pkit.getCurrentProject().getEntities(&quot;containsProcess@SYSTEM&quot;)
[0].getEntities(&quot;containsArtifact@SYSTEM&quot;);
for (i = 0; i &lt;artifacts.length; i++) {
 var artifacts_instances =
 artifacts[i].getEntities(&quot;containsInstance@SYSTEM&quot;);
 for (j = 0; j &lt;artifacts_instances.length; j++) {
 var artifacts_revisions =
 artifacts_instances[j].getEntities(&quot;containsRevision@SYSTEM&quot;);
 if (artifacts_…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started_installing_birt?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Installing the BIRT Designer</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started_installing_birt?rev=1773421097&amp;do=diff</link>
        <description>Installing the BIRT Designer

	*  Download the latest version from the Stages BIRT Designer from the Method Park download server.
			*  Note: Please contact your support team to get a proper download link.

	*  Create a folder somewhere on your computer.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_getting_started?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Getting Started</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_getting_started?rev=1773421097&amp;do=diff</link>
        <description>Getting Started

Installing the BIRT Designer

Customizing of the PkitMetrics.xml

Creating Stages BIRT Reports: A Basic Example

Creating Stages Data Collector

Example for a Dataset Script</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_issues?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Issues</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_issues?rev=1773421097&amp;do=diff</link>
        <description>Known Issues

Problem with numreic result column names

If using a data set containing a numeric result column name then this could cause problems, see

	*  &lt;https://bugs.eclipse.org/bugs/show_bug.cgi?id=321104&gt;
	*  &lt;https://bugs.eclipse.org/bugs/show_bug.cgi?id=375302&gt;

Warning: Do not use numeric reult column names.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_configprop?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuration Properties</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_configprop?rev=1773421097&amp;do=diff</link>
        <description>Configuration Properties

metrics.dataCollector.importPackages

Default Value: java.util, java.lang, java.text, java.io, java.math, java.sql, java.net, java.util.regex, javax.xml.parsers, org.xml.sax, org.w3c.dom, javax.xml.xpath, net.sf.mpxj.reader, org.apache.poi.ss.usermodel</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers_examples?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>CronTrigger Examples</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers_examples?rev=1773421097&amp;do=diff</link>
        <description>CronTrigger Examples

For those unfamiliar with “cron”, this means being able to create a firing schedule such as: “At 8:00am every Monday through Friday” or “At 1:30am every last Friday of the month”.

Examples
ExpressionMeaning“0 0 12 * * ?</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers_expression?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Cron-Expression Reference</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers_expression?rev=1773421097&amp;do=diff</link>
        <description>Cron-Expression Reference

Cron expressions provide the ability to specify complex time combinations such as “At 8:00am every Monday through Friday” or “At 1:30am every last Friday of the month”.

Cron expressions are comprimsed of 6 required fields and one optimal field separated by a white space. The fields respectively are described as follows:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>CronTriggers</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_crontriggers?rev=1773421097&amp;do=diff</link>
        <description>CronTriggers

CronTrigger Examples

Cron-Expression Reference</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_dataset?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Dataset Methods</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_dataset?rev=1773421097&amp;do=diff</link>
        <description>Dataset Methods

Description: The dataset class and its methods are used to store values in a Data Set/Data Collector script. These values can then be used in the BIRT Designer report or will be stored in the metric database.
NameReturn ValueDescription</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_globalvariables?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Global Variables</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_globalvariables?rev=1773421097&amp;do=diff</link>
        <description>Global Variables

Description: Set of predefined global variables to be used in a Stages data set script or in a collector script.
NameDescriptionpkitStarting handle to get process informationdataset 
Collector: returns the actual project  
 
Stages data set: not defined</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_poijava?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>POI Javascript Wrapper Functions</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_poijava?rev=1773421097&amp;do=diff</link>
        <description>POI Javascript Wrapper Functions

These functions can be used to retrieve values from an Excel file using the Java POI library.


function getNumericValue(sheet,row, col) {
 Row = sheet.getRow(row);
 if (Row != null) {
 Cell = Row.getCell(col);
 if (Cell != null) {
 return(Cell.getNumericCellValue());
 }
 }
 return &quot;&quot;;
}
function getStringValue(sheet,row, col) {
 Row = sheet.getRow(row);
 Cell = Row.getCell(col);
 if (Cell != null) {
 if (Cell.getCellType() == Cell.CELL_TYPE_STRING) {
 return Ce…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references_preloadedjava?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Preloaded Java Packages</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references_preloadedjava?rev=1773421097&amp;do=diff</link>
        <description>Preloaded Java Packages
NameDescriptionjava.utilContains the collections framework, legacy collectin classes, event model, date and time facilities, internationalization, and miscellaneous utility classes (a string tokenizer, a random-number generator, and a bit array).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_references?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>References</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_references?rev=1773421097&amp;do=diff</link>
        <description>References

CronTriggers

Configuration Properties

POI Javascript Wrapper Functions

Global Variables

Dataset Methods

Preloaded Java Packages</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports_tipsandtricks?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Tips and Tricks</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports_tipsandtricks?rev=1773421097&amp;do=diff</link>
        <description>Tips and Tricks

Debugging of BIRT scripts (file based)

Debugging of Data Set scripts (data based)

Remove HTML tags from Stages element descriptions within the Data Set script

Alternating table row color

Setting Data Source Login credentials with XML file

Retrieving the parent element path

Retrieving the property key values

Switch Context to Viewing User</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custom_reports?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create Custom Reports</title>
        <link>https://doc.stagesasaservice.com/261/custom_reports?rev=1773421097&amp;do=diff</link>
        <description>Create Custom Reports

General Information

Getting Started

Accessing Data

Concepts

Tips and Tricks

References

Known Issues</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/customize_support_tile?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Add custom information to the dashboard support tile</title>
        <link>https://doc.stagesasaservice.com/261/customize_support_tile?rev=1773421097&amp;do=diff</link>
        <description>Add custom information to the dashboard support tile

Add the following properties to your language *.properties files (global definition in conf/local.properties or metamodel specific in localization/*.properties) to provide custom information for the stages users.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/custum_reports_generalinfo_architecture?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Architecture</title>
        <link>https://doc.stagesasaservice.com/261/custum_reports_generalinfo_architecture?rev=1773421097&amp;do=diff</link>
        <description>Architecture


Report Designer BIRT Report Designer. Desktop application which will be used to design the reports. The output is a XML Report Design file.XML Report Design This file will be uploaded on a Stages metric page. This file will be processed (rendered) by the Report Engine (part of the Stages distribution).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dashboard?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use the Landing Page</title>
        <link>https://doc.stagesasaservice.com/261/dashboard?rev=1773421097&amp;do=diff</link>
        <description>Use the Landing Page

The landing page acts as the central hub for information and is accessible through the Home icon. It is global, so it will always show the same content, regardless of which workspace you are in. Typically landing page will be used to display your organization logo, as well as facilitate navigation to other pages in Stages by providing direct links or clickable images.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dependentelements?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>States and Quality Levels for Work Products</title>
        <link>https://doc.stagesasaservice.com/261/dependentelements?rev=1773421097&amp;do=diff</link>
        <description>States and Quality Levels for Work Products

A Work Product represents the artifact, outcome, or a deliverable created or consumed during the process. In the overall context of a process, a work product progresses through various states when handled by multiple activities. This state change can happen within a workflow or through the course of different workflows during the product or program lifecycle. For example, a work product like &#039;Software Project Plan&#039; would iteratively go through a chang…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/description_templates?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Description Templates</title>
        <link>https://doc.stagesasaservice.com/261/description_templates?rev=1773421097&amp;do=diff</link>
        <description>Use Description Templates

Description templates are useful to produce high-quality process content. With these templates, you can make it easier for modelers to keep a consistent structure when describing process content.

Create Description Templates</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/descriptions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create and Edit Descriptions</title>
        <link>https://doc.stagesasaservice.com/261/descriptions?rev=1773421097&amp;do=diff</link>
        <description>Create and Edit Descriptions

Quick Reference

Interface

Concepts

Content Migration

References

Known Limitations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/diagnose_problems?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Diagnose Problems</title>
        <link>https://doc.stagesasaservice.com/261/diagnose_problems?rev=1773421097&amp;do=diff</link>
        <description>Diagnose Problems

To diagnose problems, a diagnostic report can be sent to the Stages Customer Care team for further processing.

How to generate the diagnostic report

Log in as a user with administrative privileges. In the Administration menu, scroll down to &#039;Further Information&#039; and click on &#039;Runtime Information.&#039; A PKS or PKS2 file is downloaded, that contains all information needed for diagnosis. The file is encrypted and can only be decrypted by the Customer Care team. Please send the PKS…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_cms?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create a New CMS Profile</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_cms?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Integration

Create a New CMS Profile

A CMS profile is required for working with Dimensions files in Stages. It defines access details for the repository location and additional settings.

Steps:

	*  Entering a Name for a CMS profile is optional. If no name is specified, a display name for the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_config_global?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Global CMS Properties</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_config_global?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Configuration

Global CMS Properties

These following properties influence the general behavior of the Dimensions interface. The default values of the properties will be used if they are not explicitly defined and overwritten in the Dimensions cms-type section.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_config_host_prop?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Host-specific Properties</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_config_host_prop?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Configuration

Host-specific Properties

DatabaseName

	*  Default Value: N/A
	*  Description: The name of the Dimensions database to connect to.

DatabaseConnection

	*  Default Value: N/A
	*  Description: The name of the Dimensions database connection.

User

	*</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_config_host?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Host Sections</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_config_host?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Configuration

Host Sections

For each Dimensions server that shall be accessible by Stages a cms-host section must be added to the Dimensions cms-type section in PKitConfig.xml. The defined hosts can be referenced in Stages CMS profiles. The following attributes can be dpecifies for a host whereas you have to provide values for the attribute ident and name.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Interface Configuration</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_config?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Integration

Interface Configuration

The configuration is done in the Stages configuration file PKitConfig.xml. Dimensions interface properties are defined in the section “cms” (see example configuration below) were the cms interface types are defined that shall be used on the Stages server.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Limitations</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_limitations?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Integration

Known Limitations

  Only one request relationship type selectable

	*  Description: In the same dialog where the state of the file is changed, request ids can be specified to which the file shall be related and the relationship type can be selected. Even though you can enter multiple request ids (commaseparated) you can only choose one releationship type for all of them.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions_users?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Users and Permissions</title>
        <link>https://doc.stagesasaservice.com/261/dimensions_users?rev=1773421097&amp;do=diff</link>
        <description>Dimensions Integration

Users and Permissions

Each user who performs Dimensions configuration management operations via Stages needs a Dimensions user account. The user will be prompted once for his Dimensions credentials when they are needed. After successful authentication, Stages reuses the credentials for subsequent operations of the user, until an authentication attempt fails.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/dimensions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrate with Dimensions</title>
        <link>https://doc.stagesasaservice.com/261/dimensions?rev=1773421097&amp;do=diff</link>
        <description>Integrate with Dimensions

Users and Permissions

Interface Configuration

	*  Global CMS Properties
	*  Host Sections
	*  Host-specific Properties

Create a New CMS Profile

Known Limitations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/document_lifestyles?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Document Lifecycles</title>
        <link>https://doc.stagesasaservice.com/261/document_lifestyles?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

Document Lifecycles

Stages supports the application of document lifecycles on document instances. These lifecycles are configured in the process metamodel. For each document lifecycle, certain document states are defined, which can be illustrated by a color/style. The following is a section from the process metamodel. It specifies the usage of the color</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/downloads?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Add Templates, Checklists and other Guidance Materials</title>
        <link>https://doc.stagesasaservice.com/261/downloads?rev=1773421097&amp;do=diff</link>
        <description>Add Templates, Checklists and other Guidance Materials

Guidance material provides information on HOW to perform processes. It can come in different formats such as templates, checklists, training, tools, or practices.

Associate the formats to the element types best-suited for that type. For example, practices typically explain how to perform an activity; templates usually pertain to work products.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/edit_tables?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to add tables to process descriptions</title>
        <link>https://doc.stagesasaservice.com/261/edit_tables?rev=1773421097&amp;do=diff</link>
        <description>How to add tables to process descriptions

TBD:

Tables with images: Images are only scaled down if a table width is specified

If a table contains images and the table does not fit into the browser window, it is shown in the mobile view:

TBD Mobile Table View</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_anchors?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Anchors</title>
        <link>https://doc.stagesasaservice.com/261/editor_anchors?rev=1773421097&amp;do=diff</link>
        <description>Anchors

An anchor is used to point to a specific position in the text. You might link from the bottom of a long page to the top of the page, or link from an item in a Tabel of Contents to the corresponding item where it appears on the page.

Create an Anchor</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_concepts?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Concepts</title>
        <link>https://doc.stagesasaservice.com/261/editor_concepts?rev=1773421097&amp;do=diff</link>
        <description>Concepts

Copy and Paste

Styles

Tables

Anchors

Links

Resources

Directives

Unmanaged Sections</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_copypaste?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Copy and Paste</title>
        <link>https://doc.stagesasaservice.com/261/editor_copypaste?rev=1773421097&amp;do=diff</link>
        <description>Copy and Paste

When copying and pasting content from other sources (e.g Microsoft Word, Web Browser) all data is transfered to the Stages Server and a HTML validation is performed. The allowed HTML tags and the validation schema can be found in the related links.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_directives?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Directives</title>
        <link>https://doc.stagesasaservice.com/261/editor_directives?rev=1773421097&amp;do=diff</link>
        <description>Directives

Directives are used to either hide text content in the browser display view or in the print view.

The following directives can be added to the text:
IconDescriptionnodisplay --&gt;Start of a no display section&lt;--nodisplayEnd of a no display section</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_interface?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Interface</title>
        <link>https://doc.stagesasaservice.com/261/editor_interface?rev=1773421097&amp;do=diff</link>
        <description>Interface

The Stages Editor consists of 4 main parts:

	*  Toolbar- the section at the top of the editor containing grouped menu buttons that give you access to various functions of the Stages Editor.
	*  Editing Area  - the space below the toolbar where you type your text and add media.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Limitations</title>
        <link>https://doc.stagesasaservice.com/261/editor_limitations?rev=1773421097&amp;do=diff</link>
        <description>Known Limitations
ComponentDescriptionText Color PluginThe color picker for text coloring does not show correct color when reopening.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_links?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Links</title>
        <link>https://doc.stagesasaservice.com/261/editor_links?rev=1773421097&amp;do=diff</link>
        <description>Links
Element TypeLink TypeCommentProcess ElementsInternal LinkAll metamodel element types except of resources (see below) and annotations/comments can be linked.ResourcesInternal LinkThe following resource types can be linked: examples, checklists, internal checklists, arbitrary description, arbitrary file, prototype, and template.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_migration?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Content Migration</title>
        <link>https://doc.stagesasaservice.com/261/editor_migration?rev=1773421097&amp;do=diff</link>
        <description>Content Migration

Migration of text written in the old rich-text editor (Stages 5.x) can be performed in two ways:

	*  on demand/step by step - this is the Stages Web method
	*  bulk/all in one - this is the Stages Composer method

Both methods use the same cleanup algorithms.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_reference?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Quick Reference</title>
        <link>https://doc.stagesasaservice.com/261/editor_reference?rev=1773421097&amp;do=diff</link>
        <description>Quick Reference

Keyboard Shortcuts

Keyboard Shortcuts General
Keyboard ShortcutDescriptionCtrl+SSave and close the Stages Editor
Keyboard Shortcuts Navigation
Keyboard ShortcutDescriptionHomeJumps to the beginning of the lineCtrl+HomeJumps to the beginning of the document</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_references?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>References</title>
        <link>https://doc.stagesasaservice.com/261/editor_references?rev=1773421097&amp;do=diff</link>
        <description>References

Predefined Styles

The following styles are predefined in the default installation:
NameStyle idcss codeStandardpDefault paragraph stylingHeading 1h1 

h1 {
 font-weight:bold;
 font-size: 125%;
 margin: 0.8em 0 0.5em 0;
}

Heading 2h2 

h2 {
 font-weight:bold;
 font-size: 120%;
 margin: 0.8em 0 0.5em 0;
}</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_resources?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Resources</title>
        <link>https://doc.stagesasaservice.com/261/editor_resources?rev=1773421097&amp;do=diff</link>
        <description>Resources

Embedding a resource means that the content is visible in the description. It is not copied into the description. As soon as the embedded resource is changed all places where it is embedded will see the new content. The following resources are available to embed into a description text:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_styles?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Styles</title>
        <link>https://doc.stagesasaservice.com/261/editor_styles?rev=1773421097&amp;do=diff</link>
        <description>Styles

Styles are pre-defined combinations of various formatting options that make it easier to keep the presentation of the text uniform. Since a style often contains a number of features at once, when you want to customize the way a text fragment looks, you do not need to change a font, its size, or text and background color separetly.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_tables?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Tables</title>
        <link>https://doc.stagesasaservice.com/261/editor_tables?rev=1773421097&amp;do=diff</link>
        <description>Tables

In the description of an element, you can include tabular information. Simple tables are best; large and complex tables can be challenging to produce and consume on smaller devices and in print.

Insert a Table

	*  Press the Table  button on the toolbar. The</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/editor_unmanaged?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Unmanaged Sections</title>
        <link>https://doc.stagesasaservice.com/261/editor_unmanaged?rev=1773421097&amp;do=diff</link>
        <description>Unmanaged Sections

Unmanaged Sections provide the ability to insert HTML code into a description text. They are called “unmanaged” because Stages does not validate this HTML code. Stages sends this code to the web browser unchanged.

 Considering IT security, this feature is disabled by default.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/element_abbreviations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to use Abbreviations for Element Names</title>
        <link>https://doc.stagesasaservice.com/261/element_abbreviations?rev=1773421097&amp;do=diff</link>
        <description>How to use Abbreviations for Element Names

When to use abbreviations

Edit abbreviations

Implicitely create element abbreviations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/email_feedback?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title></title>
        <link>https://doc.stagesasaservice.com/261/email_feedback?rev=1773421097&amp;do=diff</link>
        <description>Not longer applicable</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/email_notification?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>E-mail Notifications</title>
        <link>https://doc.stagesasaservice.com/261/email_notification?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

E-mail Notifications

The Stages e-mail notification service informs Stages users about Process Release tasks. A Stages administrator gets informed about the result of regular background tasks like the CMS prefetch.

Before using this notification service, a few configuration parameters must be set in the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/enable_support?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Enable Support for Kerberos Autologin in Stages</title>
        <link>https://doc.stagesasaservice.com/261/enable_support?rev=1773421097&amp;do=diff</link>
        <description>Deployment Guide

Enable Support for Kerberos Autologin in Stages

By default, Autologin is configured to be off. To enable Kerberos Autologin, set the configuration properties “autologin.spnego.enabled” to “true”.

&lt;property name=“autologin.spnego.enabled</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/execution?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage process execution</title>
        <link>https://doc.stagesasaservice.com/261/execution?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Manage process execution

Execution

Modern PLM and ALM tool chains can be used to execute parts of the engineering process. With Stages, these processes can be automatically deducted from a model-based approach. Specific PLM and ALM platforms can be automatically configured with project-specific processes which can be connected to data repositories. This allows the user to have transparency across multiple data sources and tools.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/fileaccess?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage file access</title>
        <link>https://doc.stagesasaservice.com/261/fileaccess?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Manage file access

All files in the entire process do not pertain to certain roles or users so you can manage who has access to files. You can manage files under the management tab on the left-side menu. From here click the File Management tab. There are two sections for file management, work products and guidance.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/files?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Work with Files</title>
        <link>https://doc.stagesasaservice.com/261/files?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Work with Files

Files in Stages can be very useful when working with guidance and work products. When on a work product page, the specific documentation that needs to be completed can be right in the folder with the job. Files in the guidance folder help the user understand the process in a deeper sense. On the specific work product or guidance page, there is a file section where you can add, download, upload, etc.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/generative_ai?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create process content using AI</title>
        <link>https://doc.stagesasaservice.com/261/generative_ai?rev=1773421097&amp;do=diff</link>
        <description>Create process content using AI

Using Generative AI, Stages can help to draft activity, role, and work product descriptions or create a first set of activities for a workflow. As a modeler, you can pick from a predefined set of templates and select the best matching option for the content Stages AI should generate for you.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/guidance_cms?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Where to best store Checklists and Templates</title>
        <link>https://doc.stagesasaservice.com/261/guidance_cms?rev=1773421097&amp;do=diff</link>
        <description>Where to best store Checklists and Templates

There are two options where to store your checklists and templates.

Upload them directly to Stages if you would like to

	*  version and release them together with your processes
	*  have full change control through Stages</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/import_reference_model?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>This page has been replaced</title>
        <link>https://doc.stagesasaservice.com/261/import_reference_model?rev=1773421097&amp;do=diff</link>
        <description>This page has been replaced

Please see How to install Reference Models and update your bookmarks.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/import_reports?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Import New Reports</title>
        <link>https://doc.stagesasaservice.com/261/import_reports?rev=1773421097&amp;do=diff</link>
        <description>Import New Reports

Stages supports metrics and reports by integrating the BIRT system. Typically these reports are designed and sent by the Method Park team. However, if desired there is also report training available.

Create Report element

To upload a new report navigate to Reports.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/import-processes?rev=1777289911&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-27T11:38:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Import a Process</title>
        <link>https://doc.stagesasaservice.com/261/import-processes?rev=1777289911&amp;do=diff</link>
        <description>Import a Process

A predefined process in zip file format can be imported into Stages using the Import feature.

	*  Create the workspace where the process has to be imported.
	*  Next navigate to the Process  tab in that workspace and select the Import</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/install?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Basic Installation</title>
        <link>https://doc.stagesasaservice.com/261/install?rev=1773421097&amp;do=diff</link>
        <description>Basic Installation

Perform basic installation on Windows

Download and install Java Development Kit 17

	*  see System Requirements for supported variants

Database installation with MySQL 8.0

	*  Get MySQL database dump from Stages Support
	*  Download MySQL Installer for MySQL 8.0</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/instantiate?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Instantiate a Process in a Workspace</title>
        <link>https://doc.stagesasaservice.com/261/instantiate?rev=1773421097&amp;do=diff</link>
        <description>Instantiate a Process in a Workspace

Process instantiation is using a standard process and tailoring it for a specific project, program, or team context.

Some advantages of process instantiation are

	*  The version of a process instance can be kept stable. Even if the standard process from which it was initially derived from is being updated, the instance will not be impacted until a decision is being made to update it to a newer version.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/jira_feedback?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process feedback in Jira</title>
        <link>https://doc.stagesasaservice.com/261/jira_feedback?rev=1773421097&amp;do=diff</link>
        <description>Process feedback in Jira

With this feature, users are able to provide feedback directly while navigating through the process. The feedback is created as a Jira item and can be triaged, planned, and tracked within Jira. Every generated Jira item contains a link back to the original process element where the feedback was being created, so full traceability of process change requests is assured.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/kerberos_autologin?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configure Kerberos Autologin</title>
        <link>https://doc.stagesasaservice.com/261/kerberos_autologin?rev=1773421097&amp;do=diff</link>
        <description>Configure Kerberos Autologin

 WARNING:  Starting with Stages 7.11, Kerberos Autologin (SPNEGO) is not supported anymore. Administrators are advised to migrate to the newer SAML Single Sign On system.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/kerberos_faq?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Frequently Asked Questions</title>
        <link>https://doc.stagesasaservice.com/261/kerberos_faq?rev=1773421097&amp;do=diff</link>
        <description>Kerberos Autologin

Frequently Asked Questions

Will SPNego work with HTTP proxies?

No and yes. To avoid difficulties, this manual recommends to disable proxy usage for the Stages server via browser configuration.

The problem is that the SPNego authentication headers might get modified or even be removed by a proxy. Furthermore a proxy has to take care of not sharing authenticated connections between several clients. There are proxy implementations which are capable of handling SPNego sessions…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_autocreation?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring Auto-Creation</title>
        <link>https://doc.stagesasaservice.com/261/ldap_autocreation?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Configuring Auto-Creation

With user auto-creation enabled it is possible to create new users automatically on the fly when they try to login into Stages even if a full synchronization has not been performed yet.

Using the ondemandFilterthe user will be searched for in one of the LDAP repositories and if found automatically synchronized with the Stages user database. This way it is possible to increase synchronization intervals or make use of the “ondemand” synchronization…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_basics?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>LDAP Basics</title>
        <link>https://doc.stagesasaservice.com/261/ldap_basics?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

LDAP Basics

LDAP is the abbreviation of Lightweight Directory Access Protocol, a set of protocols for accessing information directories. It allows quick, efficient searches of directory services. LDAP is based on the standards contained within the X.500 standard, but is significantly simpler. Built around Internet technologies, LDAP makes it possible to easily update and query directory services over standard TCP/IP connections, and includes a host of powerful features, in…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_checklist?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Checklist for Customer Configuration</title>
        <link>https://doc.stagesasaservice.com/261/ldap_checklist?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Checklist for Customer Configuration

This checklist contains the main subjects that need to be clarified in advance of a LDAP connection:

	*  Which LDAP providers will be used and what is their URL (including port and base domain for user selection)?</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_config_authenication?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring Authentication</title>
        <link>https://doc.stagesasaservice.com/261/ldap_config_authenication?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Configuring Authentication

Every user is authenticated against the LDAP directory server where it was synchronized from. For the synchronization it may be necessary to specify a certain LDAP user who will be used to connect to the LDAP directory server and to query that server. This user can be specified using the ldap-query-user tag.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_config_directories?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuration of LDAP Directories to be Synchronized</title>
        <link>https://doc.stagesasaservice.com/261/ldap_config_directories?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Configuration of LDAP Directories to be Synchronized

URL Attribute

Key Attribute

Optional Attributes

The ondemandFilter Attribute</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_ex_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Example Configurations</title>
        <link>https://doc.stagesasaservice.com/261/ldap_ex_config?rev=1773421097&amp;do=diff</link>
        <description>Configure LDAP

Example Configurations

An example configuration followed by an explanation:



&lt;ldap refreshIntervalMinutes=&quot;120&quot; maximumDeletionPercentage=&quot;5&quot;&gt;
 &lt;ldap-provider
 url=ldap://server.example.com:389/dc=domain,dc=example,dc=com
 key=&quot;username&quot;
 searchFilter=&quot;(objectClass=user*)&quot;
 defaultRoles=&quot;true&quot;
 adoptUsers=&quot;true&quot;
 matchUsersMode=&quot;username&quot;&gt;

 &lt;ldap-authentication
 type=&quot;simple&quot;
 principal=&quot;cn=%,ou=example,dc=test,dc=example,dc=com&quot;/&gt;
 &lt;ldap-query-user name=&quot;queryuser&quot; credentia…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_gen_info?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>LDAP General Information</title>
        <link>https://doc.stagesasaservice.com/261/ldap_gen_info?rev=1773421097&amp;do=diff</link>
        <description>LDAP Configuration

LDAP General Information

Information about users, groups, and hosts of an organisation is usually stored in corporate directory systems. To implement a Single-Sign-On (SSO) policy or at least a Single-Password-Strategy, these systems are often used as single source, e.g. for user password information. Therefore it is reasonable to synchronize the Stages user database with these directory systems.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_getting_started?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Getting Started</title>
        <link>https://doc.stagesasaservice.com/261/ldap_getting_started?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Getting Started

The synchronization of the Stages user database with a LDAP directory is configured in a specific section of the config.xml file. The LDAP configuration is defined in the ldap-provider tag section.

 The config.xml file can be found under:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_global_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Global LDAP Configuration</title>
        <link>https://doc.stagesasaservice.com/261/ldap_global_config?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Global LDAP Configuration

In order to keep the user information in the Stages database up-to-date, synchronization with a LDAP directory server is a recurring process. Therefore the LDAP configuration starts with setting the refreshIntervalMinutes attribute specifying a minute interval between two synchronization runs.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_hints?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Hints for Specific LDAP Server Products</title>
        <link>https://doc.stagesasaservice.com/261/ldap_hints?rev=1773421097&amp;do=diff</link>
        <description>LDAP Configuration

Hints for Specific LDAP Server Products

Microsoft Active Directory Server (ADS)

When the standard ADS layout is used by the ADS administrator, user entries can be found in the “CN=Users“ part of the directory. For larger organizations, this section is normally divided into different subsections to increase scalability and manageability.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_key_attribute?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Key Attribute</title>
        <link>https://doc.stagesasaservice.com/261/ldap_key_attribute?rev=1773421097&amp;do=diff</link>
        <description>Configuration of LDAP Directories to be Synchronized

Key Attribute

Every object in a LDAP directory is uniquely identifiable by its distinguished name (DN). To specify a certain LDAP user entry for authentication purposes it is necessary to build up its distinguished name.

Given the example above, the DN for a user entry could be:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_language?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Language Reference</title>
        <link>https://doc.stagesasaservice.com/261/ldap_language?rev=1773421097&amp;do=diff</link>
        <description>LDAP Configuration

Language Reference

TBD</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_log_information?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Log Information</title>
        <link>https://doc.stagesasaservice.com/261/ldap_log_information?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Log Information

All modifications to the Stages user database caused by LDAP synchronization (creation, modification or deletion of user entries) are logged in a special logfile named “synchro.log“. This logfile is located in the same folder as the other Stages logfiles (i.e. Stages installation folder).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_mapping?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Mapping LDAP Attributes to Stages</title>
        <link>https://doc.stagesasaservice.com/261/ldap_mapping?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Mapping LDAP Attributes to Stages

LDAP user attributes are mapped to Stages user attributes during synchronization. The corresponding mapping tags are thereby nested in the ldap-provider tag, so that a valid specification structure looks as follows:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_ondemand?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>The ondemandFilter Attribute</title>
        <link>https://doc.stagesasaservice.com/261/ldap_ondemand?rev=1773421097&amp;do=diff</link>
        <description>Configuration of LDAP Directories to be Synchronized

The ondemandFilter Attribute

This attribute is required for user auto-creation and/or on-demand synchronization mode. It allows the Stages system to query the LDAP server for specific users by their Stages login name. The attribute value a query filter like the searchFilter attribute, except that it is meant for unique queries.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_optional_attributes?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Optional Attributes</title>
        <link>https://doc.stagesasaservice.com/261/ldap_optional_attributes?rev=1773421097&amp;do=diff</link>
        <description>Configuration of LDAP Directories to be Synchronized

Optional Attributes

The defaultRoles Attribute

The defaultRoles attribute is used to set whether a newly created user will automatically be assigned to the roles of the Stages “default“ user. To enable that behavior, the parameter has to be set to “true“. This feature is disabled by default.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_overview?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Overview</title>
        <link>https://doc.stagesasaservice.com/261/ldap_overview?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Overview

Configuring LDAP is a customer specific task. Because LDAP directories can be structured arbitrarily regarding their directory tree layout, attribute names, and attribute values, configuring LDAP synchronization is very specific to each installation.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_ssl?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring Synchronization via SSL</title>
        <link>https://doc.stagesasaservice.com/261/ldap_ssl?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Configuring Synchronization via SSL

To enforce encrypted transmission for synchronization, SSL can be used as a transport protocol. This encrypts sensitive information (e.g. passwords) before transferring them over the network.

Before using LDAP over SSL, the appropriate certificate of the LDAP server has to be added to the Java truststore. This certificate should first be exported into a DER format file.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_sync?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>LDAP Synchronization</title>
        <link>https://doc.stagesasaservice.com/261/ldap_sync?rev=1773421097&amp;do=diff</link>
        <description>LDAP Configuration

LDAP Synchronization

Overview

LDAP Basics

Getting Started

Global LDAP Configuration

Configuration of LDAP directories to be synchronized

Mapping LDAP Attributes to Stages

Selection of User Entries to be Synchronized

Configuring Authentication

Configuring Synchronization via SSL

Configuring Auto-Creation

Testing a LDAP Configuration

Log Information

Checklist for Customer Configuration</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_testing?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Testing a LDAP Configuration</title>
        <link>https://doc.stagesasaservice.com/261/ldap_testing?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Testing a LDAP Configuration

In order to test your LDAP configuration, e.g. after it has been modified, the synchronization attribute of the global ldap tag should be set to “nomodify“. The log file “synchro.log“ can then be analyzed for synchronization actions that would happen with synchronization enabled.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_url_attribute?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>URL Attribute</title>
        <link>https://doc.stagesasaservice.com/261/ldap_url_attribute?rev=1773421097&amp;do=diff</link>
        <description>Configuration of LDAP Directories to be Synchronized

URL Attribute

The url attribute is used to set the LDAP URL of the server to be queried. The attribute is structured in the following way:

&lt;ldap&gt;:&lt;ldap-server&gt;:&lt;port&gt;/&lt;ldap_directory_to_be_queried&gt;

The following table describes how to fill this schema with concrete values:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_useful_info?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Useful Information</title>
        <link>https://doc.stagesasaservice.com/261/ldap_useful_info?rev=1773421097&amp;do=diff</link>
        <description>LDAP Configuration

Useful Information

Error codes and their causes:

http://support.microsoft.com/kb/218185</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap_user_entries?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Selection of User Entries to be Synchronized</title>
        <link>https://doc.stagesasaservice.com/261/ldap_user_entries?rev=1773421097&amp;do=diff</link>
        <description>LDAP Synchronization

Selection of User Entries to be Synchronized

If not all users of a specified LDAP directory should be synchronized with the Stages user database, it is possible to define match and ignore filters respectively.

NOTE: Both match and ignore filters are applied after the users are retrieved from the LDAP directory. In order to limit the number of user entries transferred from the directory server, an appropriate search filter should be specified.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ldap?rev=1775670835&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-08T17:53:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configure LDAP</title>
        <link>https://doc.stagesasaservice.com/261/ldap?rev=1775670835&amp;do=diff</link>
        <description>Configure LDAP

User synchronization via LDAP is not supported anymore. Please migrate to SAML for single sign on.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/licenses?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Understand and Assign User Licenses</title>
        <link>https://doc.stagesasaservice.com/261/licenses?rev=1773421097&amp;do=diff</link>
        <description>Understand and Assign User Licenses

Every user needs to be assigned to a specific user license to be able to use Stages.

License Types

The following license types are supported.

Process Modeler (MODEL)

	*  Model processes
	*  Create and release process versions</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/links?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage External Links to Process Content</title>
        <link>https://doc.stagesasaservice.com/261/links?rev=1773421097&amp;do=diff</link>
        <description>Manage External Links to Process Content

It is possible to directly link to process content from outside of Stages (“deep links”).

Simply copy the URL from the browser and put it in a document or web page.

&lt;https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a5f9e2&amp;media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/79/links.png&gt;

If the user is not logged in when following the link, the login dialog will show up. After a successful login, the respective co…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/local_news?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Local News Application Categories</title>
        <link>https://doc.stagesasaservice.com/261/local_news?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

Local News Application Categories

The Stages news application categories can also be configured individually. That means, categories can be removed or new categories can be added. This is done in the Stages configuration file named  &lt;PKITHOME&gt;/WEB-INF/conf/PKitConfig.xml</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/local_style_custom?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Local Style Customization</title>
        <link>https://doc.stagesasaservice.com/261/local_style_custom?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

Local Style Customization

TBD</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/lost_found?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to handle elements in LOST+FOUND</title>
        <link>https://doc.stagesasaservice.com/261/lost_found?rev=1773421097&amp;do=diff</link>
        <description>How to handle elements in LOST+FOUND

Root cause for LOST+FOUND 

If an process element is removed, but other objects—such as process elements, files, or user assignments—depend on that element and Stages did not receive an explicit order to delete them, those dependent objects are moved to LOST+FOUND to prevent them from being deleted.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/maintenance_mode?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Schedule and Manage System Maintenance</title>
        <link>https://doc.stagesasaservice.com/261/maintenance_mode?rev=1773421097&amp;do=diff</link>
        <description>Schedule and Manage System Maintenance

Especially in large installations that cover a global user base, maintenance windows where Stages is not available need to be scheduled and announced to the users in advance.

Maintenance can be announced via the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/manage_process_participants?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Process Management Participants</title>
        <link>https://doc.stagesasaservice.com/261/manage_process_participants?rev=1773421097&amp;do=diff</link>
        <description>Manage Process Management Participants

Similar to other process areas, it is recommended to structure process management organizations in a role-based manner, e.g. process owners, modelers, reviewers, or approvers. To avoid a terminology conflict with the normal process roles, the process management roles in Stages are called</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/manage_process_release?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Process Release Automations</title>
        <link>https://doc.stagesasaservice.com/261/manage_process_release?rev=1773421097&amp;do=diff</link>
        <description>Manage Process Release Automations

Automations can be used for a varienty of purposes, for example to organize a controlled and documented review and approval of processes or process tailorings.

Automations consist of states, participants, and the actual automation workflows. As participants can also be used for other purposes, they are</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/manage_users_groups_permissions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage users, groups, and permissions</title>
        <link>https://doc.stagesasaservice.com/261/manage_users_groups_permissions?rev=1773421097&amp;do=diff</link>
        <description>Manage users, groups, and permissions

You can manage workspaces, users, groups and permissions from the administration tab on the left-side menu.

Users

Users can be added and settings can be changed from the users section of the administration tab.

When the users tab is clicked a list of all users is displayed, but you can filter this to just the logged in users. Click the text box that says</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/manage_workspaces?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage workspaces</title>
        <link>https://doc.stagesasaservice.com/261/manage_workspaces?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Manage workspaces

You can manage workspaces, users, groups and permissions from the administration tab on the left-side menu.

Workspaces

Creating/editing workspaces is done through the workspaces tab in the administration tab on the left-side menu. You can also organize the different workspaces into different folders for easy accessibility.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/managed_service_setup?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Managed Service</title>
        <link>https://doc.stagesasaservice.com/261/managed_service_setup?rev=1773421097&amp;do=diff</link>
        <description>Stages Managed Service

The best option is to use Stages as a Managed Service. It removes any overhead for administration or troubleshooting and you can fully focus on generating business outcomes.

Setup of Single Sign On

For best user experience, the Stages Managed Service should be integrated with your existing Single Sign On (SSO) system, e.g. Microsoft AD/Azure, Okta, or other authentication systems using SAML.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/managefileaccess?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage File Access</title>
        <link>https://doc.stagesasaservice.com/261/managefileaccess?rev=1773421097&amp;do=diff</link>
        <description>Manage File Access

Stages allows you to collaborate with users from within your organization as well as external stakeholders to conduct reviews. The nature of review will vary depending on the file and stakeholders involved. Routine files might require a simple document review, whereas other more complex processes might require a formal review process involving more stakeholders. In Stages, you can specify review lifecycle for a given workspace. You also have the flexibility to change it at wo…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/managelandingpage?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Landing Pages</title>
        <link>https://doc.stagesasaservice.com/261/managelandingpage?rev=1773421097&amp;do=diff</link>
        <description>Manage Landing Pages

A well designed landing page establishes an easier and more effective communication to users on how to navigate through process information in Stages. This is typically done by clickable images or even simple links alongwith textual descriptions. By customizing the landing page, organizations can communicate the big picture of their process landscape, as well as project or program specific information, or other information of choice.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/manageprocessversions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Process Versions</title>
        <link>https://doc.stagesasaservice.com/261/manageprocessversions?rev=1773421097&amp;do=diff</link>
        <description>Manage Process Versions

Stages processes can be baselined by using the process version feature. A modeler will always be making changes in the working version of the process, while the end users will typically only be shown the baselined valid process version.

Create a new version

To create a new process verisons, navigate to Management &gt; Process version and click or tap on the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/mandatory_manual_upgrade_steps_for_version_74?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Mandatory Manual Upgrade Steps for Version 7.4</title>
        <link>https://doc.stagesasaservice.com/261/mandatory_manual_upgrade_steps_for_version_74?rev=1773421097&amp;do=diff</link>
        <description>Mandatory Manual Upgrade Steps for Version 7.4

These actions need to be executed after upgrading to Stages 7.4 from previous Stages 7 versions:

	*  Custom implementations of the de.methodpark.stages.fileservice.preset.logic.Suggestor  need to be recompiled against this Stages version.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/mandatory_manual_upgrade_steps_for_version_75?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Mandatory Manual Upgrade Steps for Version 7.5</title>
        <link>https://doc.stagesasaservice.com/261/mandatory_manual_upgrade_steps_for_version_75?rev=1773421097&amp;do=diff</link>
        <description>Mandatory Manual Upgrade Steps for Version 7.5

These actions need to be executed before/after upgrading to Stages 7.5 from previous Stages 7 versions.

General Recommendations Before Upgrading

To be safe in case of any crashes/problems during the update,</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/mcpserver?rev=1776844055&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T07:47:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages MCP Server (Beta)</title>
        <link>https://doc.stagesasaservice.com/261/mcpserver?rev=1776844055&amp;do=diff</link>
        <description>Stages MCP Server (Beta)

MCP (Model Context Protocol) has established itself as the universal way to connect LLMs (Large Language Models) and other AI systems with data sources.

Through our MCP server, AI systems can access process data managed in Stages for various purposes and use cases.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/metamodelstrategy?rev=1776704937&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-20T17:08:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Unified Configuration Metamodel Strategy</title>
        <link>https://doc.stagesasaservice.com/261/metamodelstrategy?rev=1776704937&amp;do=diff</link>
        <description>Unified Configuration Metamodel Strategy

With the goal of supporting new process modeling best practices faster than before, while still keeping the number of metamodel variants low, we will support two standard metamodels going forward.

This new strategy will be implemented with the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/model?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Model process content</title>
        <link>https://doc.stagesasaservice.com/261/model?rev=1773421097&amp;do=diff</link>
        <description>Model process content

This section assumes that you are already familiar with navigation in Stages and understand process content. It is also assumed that you are starting with an empty workspace

Click the process icon on left-side menu which directs you to the process home menu to begin. You can access a folder by clicking the specific folder on the left-side menu or on the bottom of the process home menu.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/modeling-routine-process-parameters?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Using Parameters for Generic Processes</title>
        <link>https://doc.stagesasaservice.com/261/modeling-routine-process-parameters?rev=1773421097&amp;do=diff</link>
        <description>Using Parameters for Generic Processes

 This feature is considered experimental and therefore can change without backwards compatibility. It is not available by default and has to be specifically enabled by a product consultant.  

 Please understand the limitations of this feature described in the paragraph at the end of this page.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/modeling-routine-process?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Model and Use Generic Processes</title>
        <link>https://doc.stagesasaservice.com/261/modeling-routine-process?rev=1773421097&amp;do=diff</link>
        <description>Model and Use Generic Processes

In different phases of product development cycle, some of the processes are repeated in various workflows. For example, joint review as a sub-process is executed to review different types of work product like a project plan, system design, etc. Although processes will differ, generic processes like review go through same steps to achieve the end result.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/modeling?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Model a Process</title>
        <link>https://doc.stagesasaservice.com/261/modeling?rev=1773421097&amp;do=diff</link>
        <description>Model a Process

Modeling a process enables a clear and consistent definition of processes. It also helps to eliminate redundancies and identify inefficiencies. Since the processes are stored and updated under one umbrella, Stages provides a central hub for the entire organization to use and review the modeled processes.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/msproject?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Import processes into MS Project</title>
        <link>https://doc.stagesasaservice.com/261/msproject?rev=1773421097&amp;do=diff</link>
        <description>Import processes into MS Project

Planning a project or program should be aligned with the defined process. After instantiating a process and tailoring it to the requirements of a project or program, the process data can be exported to planning tools like MS Project. For maximum flexibility, Stages can export the process data via a report to Excel, which can be directly imported into MS Project and similar planning tools.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/multi_factor_authentication?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Two factor authentication (2FA)</title>
        <link>https://doc.stagesasaservice.com/261/multi_factor_authentication?rev=1773421097&amp;do=diff</link>
        <description>Two factor authentication (2FA)

For further improving the security of Stages we enforce the usage of two factor authentication by default for local user accounts that are usually used for administrative users like the Superuser.

For SAML accounts the authentication methods are managed by your Identity Provider and not by Stages.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/multilanguage?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to manage processes in multiple languages</title>
        <link>https://doc.stagesasaservice.com/261/multilanguage?rev=1773421097&amp;do=diff</link>
        <description>How to manage processes in multiple languages

Managing a process in multiple languages is an important asset when dealing with multilingual teams. It can also be used to translate standard processes for specific product lines that are developed by teams in a different language.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/navigation?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Navigate Through Stages</title>
        <link>https://doc.stagesasaservice.com/261/navigation?rev=1773421097&amp;do=diff</link>
        <description>Navigate Through Stages

This description shows the desktop view. On a tablet or smartphone, Stages might have a different layout, but all capabilities will remain the same.

General navigation

After logging into Stages, you will see a screen similar to this:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/newprocesses?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Getting started in a new workspace</title>
        <link>https://doc.stagesasaservice.com/261/newprocesses?rev=1773421097&amp;do=diff</link>
        <description>Getting started in a new workspace

Once a workspace has been created, there is a welcome screen which provides four different mechanisms to get started.

&lt;https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=ac6367&amp;media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/welcomeprocess_1.png&gt;

1. Start with an Empty Process: To build a process from scratch, use this option. It loads the default</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/newworkspace?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating new workspace</title>
        <link>https://doc.stagesasaservice.com/261/newworkspace?rev=1773421097&amp;do=diff</link>
        <description>Creating new workspace</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ondemand_modules?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Common Element Pools</title>
        <link>https://doc.stagesasaservice.com/261/ondemand_modules?rev=1773421097&amp;do=diff</link>
        <description>Use Common Element Pools

A lot of organizations have a standard set of tools that need to be consistenly used across all processes. These elements are best managed in a central process module, typically called “Common Tools” or similar. If these sets grow beyond a certain size, integrating them all in every process might become cumbersome, especially if you are only using a few of those roles or tools in your process.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/options?rev=1777281908&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-27T09:25:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Copy, Move and Sort</title>
        <link>https://doc.stagesasaservice.com/261/options?rev=1777281908&amp;do=diff</link>
        <description>Use Copy, Move and Sort

All the process elements in Stages can potentially be copied over, moved, or sorted. Irrespective of the element type (activity, guidance, work product, etc), the steps to copy, move or sort are fairly similar.

Copy

A process element can be copied over from one folder to another in the same workspace, as well as in a different workspace. To copy multiple elements click or tap on three dots at the top level as shown in</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/overwrite?rev=1777457488&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-29T10:11:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Overwrite process elements</title>
        <link>https://doc.stagesasaservice.com/261/overwrite?rev=1777457488&amp;do=diff</link>
        <description>Overwrite process elements

When creating process variants or dedicated process instances, it might be necessary to change names, descriptions, or other attributes of process elements that originate from a process module and are therefore read-only.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/people_application?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>People Application</title>
        <link>https://doc.stagesasaservice.com/261/people_application?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

People Application

If you want to use this feature a special license is required. This license is free and you will get it from the Stages support together with an additional people application metamodel. You need to add this metamodel to your PKitProcess.xml file.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/phase_freezes_concept?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Phase Freeze Concept</title>
        <link>https://doc.stagesasaservice.com/261/phase_freezes_concept?rev=1773421097&amp;do=diff</link>
        <description>Phase Freeze Concept

Long-running projects face the challenge that either the process instance used throughout the project lifetime is getting outdated or at best does not benefit from process improvements, or the process instance gets updated on a regular basis but might demand additional tasks to be executed for process parts that were already completed in the past.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/phase_freezes_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Limitations</title>
        <link>https://doc.stagesasaservice.com/261/phase_freezes_limitations?rev=1773421097&amp;do=diff</link>
        <description>Known Limitations
TitleDescriptionWorkaroundsStable IdentitiesThe merge of the frozen baselines and the working revision depends on stable process element identities. Integration of a different Core Process into the working revision of your project (even in case the adopt option is used) will result in a merged process where all the phases of the new core process plus all the frozen phases exist.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/phase_freezes_prepare?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Prepare your Process for Phase Freeze</title>
        <link>https://doc.stagesasaservice.com/261/phase_freezes_prepare?rev=1773421097&amp;do=diff</link>
        <description>Prepare your Process for Phase Freeze

Preconditions and Rules

Preconditions

	*  Process updates need to preserve the element identities. Do not use the “adopt elements” option when importing a core process.
	*  The scope of the phase to freeze needs to be defined.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/phase_freezes_usage?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Usage</title>
        <link>https://doc.stagesasaservice.com/261/phase_freezes_usage?rev=1773421097&amp;do=diff</link>
        <description>Usage

Note: The following instructions assume that the user&#039;s preferred process views are set to “Valid Version”. Furthermore, it is assumed that email notifications are enabled in PkitConfig.xml and Stages knows about the user&#039;s email address. Finally, the user needs process application permissions.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/phase_freezes?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to freeze phases</title>
        <link>https://doc.stagesasaservice.com/261/phase_freezes?rev=1773421097&amp;do=diff</link>
        <description>How to freeze phases

Concept

Prepare your Process for Phase Freeze

Usage

Known Limitations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_architecture?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Define a Process Architecture</title>
        <link>https://doc.stagesasaservice.com/261/process_architecture?rev=1773421097&amp;do=diff</link>
        <description>Define a Process Architecture

Process Architecture is the hierarchal design of the processes. As the business undergoes changes and processes become more complex, a strong process architecture ensures that processes remain in their optimal state. Organizational strategy, structure, process ownership, and program portfolio are some of the key considerations that go into defining the architecture.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_archive?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Long-Term Archiving of Processes</title>
        <link>https://doc.stagesasaservice.com/261/process_archive?rev=1773421097&amp;do=diff</link>
        <description>Long-Term Archiving of Processes

Introduction

For business resilience and compliance reasons, important process content still needs to be retrievable after multiple decades. For that reason, Stages can generate archives with the following capabilities:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_cleanup?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Automated Process Cleanup</title>
        <link>https://doc.stagesasaservice.com/261/process_cleanup?rev=1773421097&amp;do=diff</link>
        <description>Automated Process Cleanup

Over many years of managing processes, a lot of process versions are being created. Not all of them need to be kept or be available online all the time. Therefore, Stages contains an automatic cleanup that can continuously export, archive, and delete process version based on a set of rules set by the administrators.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_execution_jira?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Execution with Atlassian Jira Data Center</title>
        <link>https://doc.stagesasaservice.com/261/process_execution_jira?rev=1773421097&amp;do=diff</link>
        <description>Process Execution with Atlassian Jira Data Center

Find conceptional guidance here: Model and Manage Process Execution

Plugin installation

Install Stages Process Execution from Atlassian Marketplace.

Project configuration

To enable Process Execution for a Jira project it is required to add two custom fields to your project:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_execution_jiracloud?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Execution with Atlassian Jira Cloud</title>
        <link>https://doc.stagesasaservice.com/261/process_execution_jiracloud?rev=1773421097&amp;do=diff</link>
        <description>Process Execution with Atlassian Jira Cloud

Find conceptional guidance here: Model and Manage Process Execution

Scripting

Find a detailed documentation on scripting for Jira Cloud Execution here: Stages Jira Cloud Scripting Documentation

Plugin installation

Install Stages Process Execution from Atlassian Marketplace.

Project configuration

To enable Process Execution for a Jira Cloud project it is required to add two custom fields to your projects issue types:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_execution_rtc?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Execution with IBM Engineering Workflow Management (RTC)</title>
        <link>https://doc.stagesasaservice.com/261/process_execution_rtc?rev=1773421097&amp;do=diff</link>
        <description>Process Execution with IBM Engineering Workflow Management (RTC)

Find conceptional guidance here: Model and Manage Process Execution

Plugin Installation and Release Notes

Download the Plugin from https://download.stages.digital/stages/rtc-plugin/

Installation Package Contents

	*  de.methodpark.rtc: the update site
	*  build.xml: the Ant installation script</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_execution?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Model and Manage Process Execution</title>
        <link>https://doc.stagesasaservice.com/261/process_execution?rev=1773421097&amp;do=diff</link>
        <description>Model and Manage Process Execution

The principal idea of the Stages Process Execution concept is to use process information in Application Lifecycle Management (ALM) Systems to work process compliant and to automate workflows.

Find technical details for the ALM Systems here:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_codebeamer?rev=1776089940&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-13T14:19:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback Codebeamer specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_codebeamer?rev=1776089940&amp;do=diff</link>
        <description>Process Feedback Codebeamer specific

not yet included in 26.1 - planned to be included in a future release

First of all, create a Codebeamer project where the feedback will be collected. If you want to collect more information than the summary and a description, you have to create a new tracker and add additional fields to it. Further information to creating and customizing trackers can be found at</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_jira_tmp?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback Jira specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_jira_tmp?rev=1773421097&amp;do=diff</link>
        <description>Process Feedback Jira specific

First of all, create a Jira project where the feedback will be collected. If you want to collect more information than the summary and a description, you have to add custom fields to your Jira project and add them to your Create Issue Screen. To locate the correct fields, use the Jira assistant</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_jira?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback Jira specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_jira?rev=1773421097&amp;do=diff</link>
        <description>Process Feedback Jira specific

First of all, create a Jira project where the feedback will be collected. If you want to collect more information than the summary and a description, you have to add custom fields to your Jira project and add them to your Create Issue Screen. To locate the correct fields, use the Jira assistant</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_link?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback Link specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_link?rev=1773421097&amp;do=diff</link>
        <description>Process Feedback Link specific

The link feedback is a generic adapter for feedback system with issue collector functionality. The Stages user is redirected via special Link to the feedback system. The user will typically see a form to create the issue. Some fields in this form will be filled out beforehand by Stages.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_polarion?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback Polarion Specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_polarion?rev=1773421097&amp;do=diff</link>
        <description>Process Feedback Polarion Specific

The Polarion Feedback adapter allows you to add work items to your Polarion instance from your Stages process. 

Example Configuration

To enable the following configuration section must be added in the conf/config.xml</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_ptcilm?rev=1776089925&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-13T14:18:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback PTC-ILM specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_ptcilm?rev=1776089925&amp;do=diff</link>
        <description>Process Feedback PTC-ILM specific

not yet included in 26.1 - planned to be included in a future release

First of all, create or choose a ILM item type where the feedback will be collected.

Stages will use the SOAP interface to create the items.

Stages config.xml</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_rtc?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback RTC specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_rtc?rev=1773421097&amp;do=diff</link>
        <description>Process Feedback RTC specific

Getting Stages ready to create Feedback as new Work Items in a RTC Project Area is simple and works as follows:

Create a new Project Area (PA) or use an existing one. For the configuration you will need the name of that PA. In this example we use</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_servicenow?rev=1776089903&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-13T14:18:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback ServiceNow Specific</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_servicenow?rev=1776089903&amp;do=diff</link>
        <description>Process Feedback ServiceNow Specific

not yet included in 26.1 - planned to be included in a future release

	*  Before integrating with ServiceNow, ensure that you have a valid ServiceNow user with access to tables that you want to use in the integration. We recommend setting up a unique ServiceNow user account to be used exclusively for</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback_sharepoint_online?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Feedback Sharepoint Online</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback_sharepoint_online?rev=1773421097&amp;do=diff</link>
        <description>Process Feedback Sharepoint Online

The Sharepoint Online Feedback adapter allows you to add items to a Sharepoint List from your Stages process. 

Prerequisites

	*  Stages 7.12.0.1 or later 
	*  Set the Application Permissions as described in the chapter permissions</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_feedback?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process feedback</title>
        <link>https://doc.stagesasaservice.com/261/process_feedback?rev=1773421097&amp;do=diff</link>
        <description>Process feedback

With this feature, users can provide feedback directly as they navigate the process. The feedback is created as a data item and can be triaged, planned, and tracked within a ticket system. Every generated item contains a link back to the original process element where the feedback was created, ensuring full traceability of process change requests.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_release_participant?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Participate in a Process Release as Reviewer or Approver</title>
        <link>https://doc.stagesasaservice.com/261/process_release_participant?rev=1773421097&amp;do=diff</link>
        <description>Participate in a Process Release as Reviewer or Approver

Every user can be part of a process release, e.g. as a reviewer or approver. Users that are set up as participants might receive an email notification and see an item in their To Do list on the landing page.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process_version_switch?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Switch between multiple versions</title>
        <link>https://doc.stagesasaservice.com/261/process_version_switch?rev=1773421097&amp;do=diff</link>
        <description>Switch between multiple versions

Process content can exist in multiple versions, e.g. the Working Version or the Valid Version.

To switch between different versions of process content, use the version selection menu on the top right. The valid version is marked with (V).



If the version you want to switch to is</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/process-import-troubleshooting?rev=1776771706&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-21T11:41:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Problems with process .zip imports</title>
        <link>https://doc.stagesasaservice.com/261/process-import-troubleshooting?rev=1776771706&amp;do=diff</link>
        <description>Problems with process .zip imports

Entity size limit exceeded

Error message:  Message: JAXP00010003: The length of entity “[xml]” is “100,001” that exceeds the “100,000” limit set by “jdk.xml.maxGeneralEntitySizeLimit”

Solution: Set the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/processexportinpdf?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Generate process exports in PDF</title>
        <link>https://doc.stagesasaservice.com/261/processexportinpdf?rev=1773421097&amp;do=diff</link>
        <description>Generate process exports in PDF

Stage provides the capability to do process exports in PDF format for any given process as well as process elements. This allows users to download the PDF which can be viewed offline, shared with external stakeholders or partners, or stored in a records management system for longterm storage.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/project_state?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Project State</title>
        <link>https://doc.stagesasaservice.com/261/project_state?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

Project State

With Stages you have the possibility to assign specific states to your projects. Of course, the assignment and in particular the change of the project state should only be done by authorized users.

Before using the project state feature, the available states have to be defined. Therefore they have to be entered into the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_cms_profile_old?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Creating a CMS Profile</title>
        <link>https://doc.stagesasaservice.com/261/ptc_cms_profile_old?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration Older than 2009

Creating a CMS Profile

Steps:

	*  Navigate to Process Workbench
	*  Click dropdown-menu “Actions / CMS Profiles”
	*  Click dropdown-menu “Actions / Create new CMS profile” and select “PTC Integrity” in the submenu
	*  The CMS profile property dialog is shown. Project related settings may be configured here</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_configuration_management?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrity Configuration Management Permissions</title>
        <link>https://doc.stagesasaservice.com/261/ptc_configuration_management?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration Older than 2009

Integrity Configuration Management Permissions

The system user specified in PKitConfig.xml for Integrity needs the following permissions:

	*  AddMember
	*  ApplyLabel
	*  CheckIn
	*  Demote
	*  FetchRevision
	*  Lock
	*  Login
	*  ModifyAuthor
	*</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_configuration_old?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Basic Configuration in PKit.xml</title>
        <link>https://doc.stagesasaservice.com/261/ptc_configuration_old?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration Older than 2009

Basic Configuration in PKit.xml


&lt;cms&gt;
&lt;cms-type name=&quot;MKS&quot; factory=&quot;de.methodpark.cms.mks.MKSFactory&quot;&gt;
&lt;!-- **** optionally specify host and port **** --&gt;
&lt;cms-property name=&quot;hostname&quot; value=&quot; HOSTNAME&quot;/&gt;
&lt;cms-property name=&quot;generic&quot; value=&quot;7001&quot;/&gt;
&lt;!-- **** optionally specify user and password **** --&gt;
&lt;cms-property name=&quot;user&quot; value=&quot;SI USERNAME&quot;/&gt;
&lt;cms-property name=&quot;password&quot; value=&quot;SI PASSWORD&quot;/&gt;
&lt;cms-property name=&quot;client&quot; value=&quot;C:\Programme\MK…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_configuring_client?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring Integrity Client</title>
        <link>https://doc.stagesasaservice.com/261/ptc_configuring_client?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration Older than 2009

Configuring Integrity Client

Steps:

	*  Enter Host Name of Integrity Server. Username and password are optional
	*  Increase maximum heap size to 512MB if sufficient RAM is available
	*  Disable System Tray Icon
	*  Since Integrity 2007 more caching-properties may be configured. An adequate caching-size will be 100</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_file_editing?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>File Editing</title>
        <link>https://doc.stagesasaservice.com/261/ptc_file_editing?rev=1773421097&amp;do=diff</link>
        <description>PTC Operations and Commands

File Editing

Adding new files as member

	*  Assign a new member to a project:
			*  add


Reading and editing of members

	*  Adding a label to a project-member: 
			*  Addlabel

	*  Adding additional text to a member-revision description:
			*  appendrevdesc</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_general?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>General Information</title>
        <link>https://doc.stagesasaservice.com/261/ptc_general?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration

General Information

Stages provides two different integrations for PTC Integrity configuration Management: The classic integration is based on SI command line client. You should use it when you have an Integrity Server release older than 2009 Service Pack 7. In other cases it is recommended to use the new web-service-based interface which has the following advantages:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_integration_new?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integration for Integrity 2009 SP7 or Newer</title>
        <link>https://doc.stagesasaservice.com/261/ptc_integration_new?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration

Integration for Integrity 2009 SP7 or Newer

Users and Permissions

Basic Configuration in PKitConfig.xml

CMS Profiles

Known Limitations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_integration_old?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integration for Integrity Releases Older than 2009 SP7</title>
        <link>https://doc.stagesasaservice.com/261/ptc_integration_old?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration

Integration for Integrity Releases Older than 2009 SP7

Integrity Operations and Commands

Integrity Configuration Management Permissions

Configuring Integrity Client

Basic Configuration in PKit.xml

Creating a CMS Profile</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_member?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Changing the State of the Member</title>
        <link>https://doc.stagesasaservice.com/261/ptc_member?rev=1773421097&amp;do=diff</link>
        <description>PTC Operations and Commands

Changing the State of the Member

	*  Upgrade a member to the next higher state of development: 
			*  promote

	*  Downgrade a member to the next lower state of development: 
			*  demote</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_new_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Basic Configuration in PKitConfig.xml</title>
        <link>https://doc.stagesasaservice.com/261/ptc_new_config?rev=1773421097&amp;do=diff</link>
        <description>PTC Integration 2009 or Newer

Basic Configuration in PKitConfig.xml

The basic configuration of the Integrity interface needs to be done in the “cms” section of PKitConfig.xml (see example below).

For each Integrity server that shall be accessed by Stages a “cms-host” section must be defined. You have to provide values for the attribute “ident” and “name”. The name must be the actual name of the Integrity server. As ident you can specify either the same value as for host name or another unique…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_new_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Limitations</title>
        <link>https://doc.stagesasaservice.com/261/ptc_new_limitations?rev=1773421097&amp;do=diff</link>
        <description>PTC Integration 2009 or Newer

Known Limitations

HTTPS

	*  Description: When https is used as a communication protocol for Stages Integrity interface, the interface web services cannot be contacted.
	*  Affected Integrity Releases: 2009 SP7
	*  (Target) Release/Hotfix: HF-S041000007- 007 for Integrity 2009 SP7.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_new_profile?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>CMS Profiles</title>
        <link>https://doc.stagesasaservice.com/261/ptc_new_profile?rev=1773421097&amp;do=diff</link>
        <description>PTC Integration 2009 or Newer

CMS Profiles

For the creation of a new CMS profile for your Stages project you can directly select Integrity in the submenu of the action “Create new CMS profile”. If you defined both interface types in PKitConfig.xml – the interface for Integrity release 2009 SP7 or newer and the interface for older Integrity releases. If you defined only one Integrity interface you will have one submenu entry named “PTC Integrity”. Entering a name for a</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_operations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrity Operations and Commands</title>
        <link>https://doc.stagesasaservice.com/261/ptc_operations?rev=1773421097&amp;do=diff</link>
        <description>PTC Integrity Integration Older than 2009

Integrity Operations and Commands

The following operations and Source-Integrity commands are executed by Stages via client si.exe:

Source Integrity Client

Sandboxes

Sessions

File Editing

Changing the State of a Member</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_sandboxes?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Sandboxes</title>
        <link>https://doc.stagesasaservice.com/261/ptc_sandboxes?rev=1773421097&amp;do=diff</link>
        <description>PTC Operations and Commands

Sandboxes

Creation of a new sandbox on the client pc:

createsandbox

Updating of all sandboxes or a single sandbox-member:

resync

Display information regarding a single sandbox (e.g. sandbox-path, projekt-path, Integrity Server):

sandboxinfo</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_sessions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Sessions</title>
        <link>https://doc.stagesasaservice.com/261/ptc_sessions?rev=1773421097&amp;do=diff</link>
        <description>PTC Operations and Commands

Sessions

End current SI-session:

exit

User log-on to Integrity Server: 

connect

User log-off from Integrity Server: 

disconnect

List all logged-in user per server:

servers</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_source_integrity_client?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Source Integrity Client</title>
        <link>https://doc.stagesasaservice.com/261/ptc_source_integrity_client?rev=1773421097&amp;do=diff</link>
        <description>PTC Operations and Commands

Source Integrity Client

Adjustment of Settings

setprefs

Patching the Source Integrity Client via Server-Stored Patches:

updateclient</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc_users?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Users and Permissions</title>
        <link>https://doc.stagesasaservice.com/261/ptc_users?rev=1773421097&amp;do=diff</link>
        <description>PTC Integration 2009 or Newer

Users and Permissions

Each user who performs Integrity configuration management operations via Stages needs an Integrity user account with appropriate permissions:

	*  AddMember Allowed
	*  AddSubproject Allowed
	*  ApplyLabel Allowed
	*  Checkin Allowed</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/ptc?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrate with PTC Integrity</title>
        <link>https://doc.stagesasaservice.com/261/ptc?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Integrate with PTC Integrity

	*  General Information
	*   Integration for Integrity 2009 SP7 and Newer
			*  Users and Permissions
			*  Basic Configuration in PKitConfig.xml
			*  CMS Profiles
			*  Known Limitations

	*   Integration for Integrity Releases Older than 2009 SP7
			*  Integrity Operations and Commands
			*  Integrity Configuration Management Permissions
			*  Configuring Integrity Client
			*  Basic Configuration in PKit.xml
			*  Creating a CMS Profile</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/quicklinkvideos?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Quick Start Guide - Videos</title>
        <link>https://doc.stagesasaservice.com/261/quicklinkvideos?rev=1773421097&amp;do=diff</link>
        <description>Quick Start Guide - Videos

Basic Series

Stages Quick Start Guide #1 - Login &amp; Change Password

In this video you will learn to login and change your password in Stages.

Stages Quick Start Guide #2 - Navigate the Main Menu

In this video you will learn how to use the main navigation in Stages.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/release_details?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>See the Process Release Information</title>
        <link>https://doc.stagesasaservice.com/261/release_details?rev=1773421097&amp;do=diff</link>
        <description>See the Process Release Information

Information about the process release is available to all process users.

From the Process start page, use the context menu at top right and select Process Release Details.

&lt;https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=f60dce&amp;media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/releasedetails_1.png&gt;A window displays the release details. The amount of information depends on whether the process release was manual or…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/releasenotes?rev=1776339692&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-16T11:41:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Release Notes for Stages 26.1</title>
        <link>https://doc.stagesasaservice.com/261/releasenotes?rev=1776339692&amp;do=diff</link>
        <description>Release Notes for Stages 26.1

We are proud to announce Stages release 26.1. It is the successor version of Stages 7.12. Subsequent versions will be numbered accordingly with the year and sequential number of its release.

Please note, that Stages 26.1 is</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/releasenotesn?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Release Notes for Stages 7.10</title>
        <link>https://doc.stagesasaservice.com/261/releasenotesn?rev=1773421097&amp;do=diff</link>
        <description>Release Notes for Stages 7.10

Version 7.10 brings a lot of new features and improvements across the entire process lifecycle.

If you are using Stages as a managed service, please feel free to request the upgrade to Stages 7.10 at any time. If you are still running Stages on-premise, please note that 7.10 is not an LTS release, so there will be no maintenance coverage as soon as the next release will come out. For customers that cannot upgrade within a 2-3 month timeframe, we suggest to remain …</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/remoteassociations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Process Interfaces</title>
        <link>https://doc.stagesasaservice.com/261/remoteassociations?rev=1773421097&amp;do=diff</link>
        <description>Manage Process Interfaces

One of the key principles of Stages is that every process element should only be modeled once. If a role, work product or guidance has been created in one workspace, it can be used in another process in a different workspace. This creates</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/reports_predefined?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Pre-Defined Standard Reports</title>
        <link>https://doc.stagesasaservice.com/261/reports_predefined?rev=1773421097&amp;do=diff</link>
        <description>Pre-Defined Standard Reports

The following reports have been created by Method Park and should be pre-installed at your Stages installation.
Report NameDescriptionDownloadProcess Version UsageThe report shows either a full tree of “What is being used</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/reports_standard?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Standard Reports</title>
        <link>https://doc.stagesasaservice.com/261/reports_standard?rev=1773421097&amp;do=diff</link>
        <description>Use Standard Reports

Stages comes with a couple of pre-installed reports. To use those reports, select the “Reports” menu in the navigation. Reports can be organized in folders, so you might find folders like “Processes” or “Tailoring” there.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/reusedescriptions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Reuse of Description Texts</title>
        <link>https://doc.stagesasaservice.com/261/reusedescriptions?rev=1773421097&amp;do=diff</link>
        <description>Reuse of Description Texts

Sometimes several process elements are essentially the same and differ only in specific additions (if at all). An example is a repetitive activity performed at different points in the process, but with each iteration/increment focused on a particular aspect. Then a part of the element&#039;s description could be identical for each occurrence, supplemented by the specific part in each case.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_advanced?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Advanced Scripting</title>
        <link>https://doc.stagesasaservice.com/261/scripting_advanced?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

Advanced Scripting

Some advanced reports and admin jobs might need to use additional Java library API to provide the requested functionality. As this might pose security risks, explicit whitelisting of such API is necessary. This can be done by providing a comma separated list of class names in the following configuration properties depending on the use case:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_artifact_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ArtifactInstanceClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_artifact_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

ArtifactInstanceClass

It corresponds to a file (artifact instance) in Stages.

ID

	*  Type: String
	*  Documentation: Database ID of the artifact instance. Can be used to create a URL

LogicalName

	*  Type: String
	*  Documentation: Name of the artifact instance as shown in Stages</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_association_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>AssociationClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_association_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

AssociationClass

It corresponds to an association in Stages.

Comment

	*  Type: String
	*  Documentation: Comments on the association

SortKey

	*  Type: Integer
	*  Documentation: Sortkey of the association

DisplayComment

	*  Type: String
	*  Documentation: Returns the rendered comment of the association</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_attribute_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>AttributeClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_attribute_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

AttributeClass

It corresponds to an attribute which is defined in the metamodel or as a process attribute in the PKitConfig.xml.

Value

	*  Type: String
	*  Documentation: Value of the attribute in the localization representation (LocalPKIT.properties or LocalPKIL_de.properties)</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_dataset?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Global Script Variables</title>
        <link>https://doc.stagesasaservice.com/261/scripting_dataset?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

Global Script Variables

Description: Set of predefined global variables to be used in Stages data set script or in a collector script.

Methods

pkit | stages | $s

	*  Description: Starting handle to get process information.
			*  getProjectsByName(str)</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_description?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Description</title>
        <link>https://doc.stagesasaservice.com/261/scripting_description?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

Description

It corresponds to a textual description in Stages. All operations will return rendered text depending of the context:

	*  metric/collector - no visualization images, no images
	*  PDF print - visualization images, images
	*  visualization - no visualization images, no images</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_entity_name?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>EnitityName</title>
        <link>https://doc.stagesasaservice.com/261/scripting_entity_name?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

EnitityName

Stages Elements can be retrieved via the getEntities-method. The string value which specifies the search was the following syntax:

[name][::namespace][@domain],[filter=“value”]

Namespace (Optional)
NameDescriptionMODEL(default)HIERARCHIC</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_link_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>LinkClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_link_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

LinkClass

Class used to represent a command link.

HTML

	*  Type: String
	*  Documentation: Returns a HTML link for the command

URL

	*  Type: String
	*  Documentation: Returns a URL link for the command</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_metric_collection?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>MetricCollectorClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_metric_collection?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

MetricCollectorClass

It corresponds to a metric data collector in Stages.

Name

	*  Type: String
	*  Documentation: Returns the name of the data collector.

SchemaDescription

	*  Type: String
	*  Documentation: Returns the schema description
			*</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_metric_report?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>MetricReportClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_metric_report?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

MetricReportClass

It corresponds to a metric report in Stages.

Name

	*  Type: String
	*  Documentation: Returns the name of the birt report

Comment

	*  Type: String
	*  Documentation: Returns the comment which is attached to the birt report via upload</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_metric_result?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>MetricResultClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_metric_result?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

MetricResultClass

It corresponds to a metric data collector result in Stages.

CreationTime

	*  Type: Date
	*  Documentation: Returns the timestamp of the creation of the metric result. Time of the collection run time.

refer SchemaDescription

	*</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_process_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ProcessClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_process_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

ProcessClass

It corresponds to a process in Stages. A project can contain 0 or more processes (including baselines).

ID

	*  Type: String
	*  Documentation: Process ID; can be used to generate internal Stages URL links

ProcessKind

	*  Type: Integer</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_process_element?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ProcessElementClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_process_element?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

ProcessElementClass

Is a kind of placeholder for all Elements in the metamodel. Each element like artifacts, roles, and metric share the same properites.

DisplayName

	*  Type: String
	*  Documentation: Name of the element

Type

	*  Type: String</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_project_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ProjectClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_project_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

ProjectClass

It corresponds to the organizational structure (“project structure”) in Stages.

ID

	*  Type: String
	*  Documentation: Project ID; can be used to generate internal Stages URL links

Name

	*  Type: String
	*  Documentation: Name of the project as visible on the Stages project naviation</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_request_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>RequestClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_request_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

RequestClass

It corresponds to an issue in the issue tracker.

refer PkitRequest.xml

	*  Type: N/A
	*  Documentation: All idents of the request (PKitRequest.xml) are available as properites.

ID

	*  Type: Integer
	*  Documentation: ID of the request</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting_user_class?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>UserClass</title>
        <link>https://doc.stagesasaservice.com/261/scripting_user_class?rev=1773421097&amp;do=diff</link>
        <description>Use Scripting

UserClass

It corresponds to a user in Stages.

Username

	*  Type: String
	*  Documentation: Returns the Username

ExternalUsername

	*  Type: String
	*  Documentation: N/A

Fullname

	*  Type: String
	*  Documentation: Returns the full name of the user</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/scripting?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use scripting</title>
        <link>https://doc.stagesasaservice.com/261/scripting?rev=1773421097&amp;do=diff</link>
        <description>Use scripting

Scripting can be used within a request configuration to bind the visibility, changeability or necessity of issue attributes to certain conditions. Mail and News Application actions also require the definition of scriptable options in order to dynamically determine the set of email receivers or the subject of an News Application entry when executing the corresponding action for instance. Stages prepares a set of objects that can be used in scripts that provide information needed to…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/search_in_stages?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Search in Stages</title>
        <link>https://doc.stagesasaservice.com/261/search_in_stages?rev=1773421097&amp;do=diff</link>
        <description>Configure the Stages Server

Search in Stages

With the search in Stages it is possible to find “words” or “elements” in all workspaces and applications. Some configuration parameters can be set in the &lt;PKITHOME&gt;/WEB-INF/conf/PKitConfig.xml  configuration file.

The following describes an example for such a configuration:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/search?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Search Process Content</title>
        <link>https://doc.stagesasaservice.com/261/search?rev=1773421097&amp;do=diff</link>
        <description>Search Process Content

The search always shows at top of every screen in Stages.

&lt;https://doc.stagesasaservice.com/lib/exe/fetch.php?media=72:search-main.png&gt;

How to Search

Click or tap in the search box and start typing what you are looking for (1). Suggestions will appear and be refined as you type. You can select a suggested result</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/security_settings?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Security Settings</title>
        <link>https://doc.stagesasaservice.com/261/security_settings?rev=1773421097&amp;do=diff</link>
        <description>Security Settings

To allow users with Internet Explorer to access Stages, set the global.secureMode.IEAccess config property in config.xml either to non_root (= all users except root) or all_users.

Unmanaged HTML sections in descriptions are an inherent security risk, because process modelers could open the system up to XSS vulnerabilities. Therefore,</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/server.xml?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>default server.xml</title>
        <link>https://doc.stagesasaservice.com/261/server.xml?rev=1773421097&amp;do=diff</link>
        <description>&lt; Configuring the TCP Ports

default server.xml


&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the &quot;License&quot;); you may not use this file except in compliance with
  the License.  You may obtain a copy of the Licen…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/setup_directory?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Setup Active Directory</title>
        <link>https://doc.stagesasaservice.com/261/setup_directory?rev=1773421097&amp;do=diff</link>
        <description>Deployment Guide

Setup Active Directory

For Stages to be able to validate the user’s Kerberos ticket it has to maintain a trust relationship with the Kerberos domain. This trust relationship is established by mapping the Stages service to an Active Directory user account and exporting the Kerberos key of that account to the Stages server. For each Stages server instance a separate trust account has to be created.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_columns?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>SharePoint Columns</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_columns?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

SharePoint Columns

A SharePoint Document Library can optionally be configured with the following pre-defined columns, and Stages will read or write meta-information of SharePoint documents. The columns&#039; names have to be configured in the cms-host section in</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_config_global?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Global CMS Properties</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_config_global?rev=1773421097&amp;do=diff</link>
        <description>Sharepoint Configuration

Global CMS Properties

These configuration properties affect the behavior of every integrated SharePoint server. The configuration of them needs to be done in the cms section of Config.xml.

Stages.server.url  (required)

	*  Default Value: N/A
	*</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_config_host_prop?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Host-specific Properties</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_config_host_prop?rev=1773421097&amp;do=diff</link>
        <description>Sharepoint Configuration

Host-specific Properties

Some properties can be defined per SharePoint server, i.e. in a cms-host section.

version.date.format  (required for Sharepoint 2007)

	*  Default Value: N/A
	*  Description: The localized date format that SharePoint is using.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_config_host?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Host Sections</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_config_host?rev=1773421097&amp;do=diff</link>
        <description>Sharepoint Configuration

Host Sections

For each SharePoint server that shall be accessed by Stages a cms-host section must be defined under the cms section in Config.xml. You have to provide values for the attribute ident and name.

	*  As ident you have to specify either the same value as for host name or another unique identifier string.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Limitations</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_limitations?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

Known Limitations

Links are *.aspx files

	*  Description: It is necessary to reference links with their full name when linking to them from Stages. SharePoint links are represented by the file extension .aspx, but SharePoint hides the extension by default.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_links?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Enable Links to a Document</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_links?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

Enable Links to a Document

If you want to use SharePoint links besides documents, you have to enable Content Types for the Document Library. This is done in the Advanced Settings menu. In the Content Types section, select Yes to allow multiple content types.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_ssl_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>SharePoint SSL Configuration</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_ssl_config?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

SharePoint SSL Configuration

Please note the following prerequisites to use SSL for the communication between Stages and SharePoint:

	*  A SharePoint 2007 server must have Windows SharePoint Services 3.0 SP3 installed.
	*  An Alternate Access Mapping must be configured for SSL. This is done in the SharePoint Central Administration under Operations and then Alternate Access Mappings.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint_users?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>SharePoint Users</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint_users?rev=1773421097&amp;do=diff</link>
        <description>SharePoint Integration

SharePoint Users

Each user who performs SharePoint configuration management operations via Stages needs a SharePoint user account. The user will be prompted once for his SharePoint credentials when they are needed. After successful authentication, Stages will reuse these credentials for subsequent operations, until an authentication attempt fails.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sharepoint?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrate with SharePoint</title>
        <link>https://doc.stagesasaservice.com/261/sharepoint?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Integrate with SharePoint

SharePoint Users

SharePoint SSL Configuration

SharePoint Columns

Enable Links to a Document

Stages CMS Configuration

	*  Global CMS Properties
	*  Host Sections
	*  Host-specific Properties

Create a new CMS Profile

Known Limitations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/smoke_test_suggestions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Suggestions for Smoke Testing an Installation</title>
        <link>https://doc.stagesasaservice.com/261/smoke_test_suggestions?rev=1773421097&amp;do=diff</link>
        <description>Suggestions for Smoke Testing an Installation

After an on-premise installation or upgrade, we suggest to run a smoke test to make sure that the application works fine within its IT environment.

The exact steps and use cases to be tested depend on your specific IT environment and custom configuration, so the following steps are</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/sql_monitor?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Database Troubleshooting</title>
        <link>https://doc.stagesasaservice.com/261/sql_monitor?rev=1773421097&amp;do=diff</link>
        <description>Database Troubleshooting

If you see problems with the data stored in Stages or if it is necessary to access the database directly, a SQL monitor capability can be used.

To access the SQL monitor, log in as root, go to Administration and click 6 times</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/stages-permission-license-matrix?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Permission-License Matrix</title>
        <link>https://doc.stagesasaservice.com/261/stages-permission-license-matrix?rev=1773421097&amp;do=diff</link>
        <description>Stages Permission-License Matrix
PermissionLicense needed for RLicense needed for MCD Administration Jobs  MOD / ADM  MOD / ADM  AI Administration  MOD / ADM  MOD / ADM  API Tokens  MOD / ADM  MOD / ADM  Chatbot  CONT / PART / PM / MOD / ADM  CONT / PART / PM / MOD / ADM</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/start_release_automation?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Initiate a Process Release</title>
        <link>https://doc.stagesasaservice.com/261/start_release_automation?rev=1773421097&amp;do=diff</link>
        <description>Initiate a Process Release

After a process model reached a certain state of maturity, it should be reviewed, potentially approved, released, and used in practice.

Several process release automations can be defined. See here for more details.

To initiate a process release, go to</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/start_sandbox?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Version 7.2</title>
        <link>https://doc.stagesasaservice.com/261/start_sandbox?rev=1773421097&amp;do=diff</link>
        <description>Stages Version 7.2

What would you like to do?

For all users

	*  Navigate through Stages
	*  Understand process content
	*  Search process content
	*  Use the dashboard
	*  Work with files
	*  How to change password

For new process modelers

	*  Model a process
	*  Add images to process descriptions
	*  Add templates, checklists, and other material
	*  Check Process Consistency
	*  Manage process versions
	*  modules

For advanced process modelers</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/start?rev=1776769495&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-21T11:04:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages Version 26.1</title>
        <link>https://doc.stagesasaservice.com/261/start?rev=1776769495&amp;do=diff</link>
        <description>Stages Version 26.1

What would you like to do? New features that come with 26.1, features with enhanced capabilities, or newly added documentation topics are marked in bold.

For all users

	*  Navigate through Stages
	*  Use the landing page
	*  Understand process content (elements, details, perspectives)
	*  Use the AI chat assistant
	*  Search process content
	*  Switch between multiple versions
	*  Work with files
	*  See the process release information
	*  Participate in a process release …</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Stages CMS Configuration</title>
        <link>https://doc.stagesasaservice.com/261/subversion_config?rev=1773421097&amp;do=diff</link>
        <description>Subversion Integration

Stages CMS Configuration

The configuration of the Subversion interface needs to be done in the cms section of PKitConfig.xml (see example configuration below).


&lt;cms&gt;
 &lt;cms-type name=&quot;Subversion&quot; factory=&quot;de.methodpark.cms.subversion.SubversionFactory&quot;&gt;
   &lt;cms-host ident=&quot;cms.exmaple.net&quot; name=&quot;https://cms.example.net&quot; displayName=&quot;Subversion Server&quot;&gt;
     &lt;cms-property name=&quot;user&quot; value=&quot;username&quot;/&gt;
     &lt;cms-property name=&quot;password&quot; value=&quot;secret&quot;/&gt;
   &lt;/cms-host&gt;
 &lt;…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_global_config?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Global Configuration Properties</title>
        <link>https://doc.stagesasaservice.com/261/subversion_global_config?rev=1773421097&amp;do=diff</link>
        <description>Subversion Configuration

Global Configuration Properties

These config properties affect the behavior of every integrated Subversion server. The configuration of them needs to be done in the cms section of PKitConfig.xml.

validatePath

	*  Default Value: ^([^~&amp;quot;#%&amp;amp;*:&amp;lt;&amp;gt;?/\\{|}.]|[^~&amp;quot;#%&amp;amp;*:&amp;lt;&amp;gt;?/\\{|}.][^~&amp;quot;#%&amp;amp;*:&amp;lt;&amp;gt;?/\\{|}]*[^~&amp;quot;#%&amp;amp;*:&amp;lt;&amp;gt;?/\\{|}.])?([\\/]([^~&amp;quot;#%&amp;amp;*:&amp;lt;&amp;gt;?/\\{|}.]|[^~&amp;quot;#%&amp;amp;*:&amp;lt;&amp;gt;?/\\{|}.][^~&amp;quot;#%&amp;amp;*:&amp;l…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_host_sections?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Host Sections</title>
        <link>https://doc.stagesasaservice.com/261/subversion_host_sections?rev=1773421097&amp;do=diff</link>
        <description>Subversion Configuration

Host Sections

For each Subversion server that shall be accessed by Stages a cms-host section must be defined under the cmssection in PkitConfig.xml. You have to provide values for the attribute ident and name.

	*  As ident  you have to specify either the same value as for host name or another unique identifier string.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_host_specific?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Host-Specific Configuration Properties</title>
        <link>https://doc.stagesasaservice.com/261/subversion_host_specific?rev=1773421097&amp;do=diff</link>
        <description>Subversion Configuration

Host-Specific Configuration Properties

Some properties can be defined per Subversion server, i.e. in a cms-host section.

User

	*  Default Value: N/A
	*  Description: You may enter the Subversion username for the Stages system account here instead of the corresponding field Username in the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_limitations?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Known Limitations</title>
        <link>https://doc.stagesasaservice.com/261/subversion_limitations?rev=1773421097&amp;do=diff</link>
        <description>Subversion Integration

Known Limitations

Known limitations that affect all Subversion servers

Supported Server Versions

	*  Description: 1.2.X, 1.3.X, 1.4.X, 1.5.X, 1.6.X, 1.7.X, 1.8.X
	*  Workarounds: N/A

 
HTTP option request must trigger authentication

	*  Description: In order to validate user credentials, the Subversion server must enforce authentication (valid-user) for HTTP Option requests</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_migration?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Migration of Legacy SVN CMS Profile</title>
        <link>https://doc.stagesasaservice.com/261/subversion_migration?rev=1773421097&amp;do=diff</link>
        <description>Subversion Integration

Migration of Legacy SVN CMS Profile

Prerequisites

	*  Configure your Subversion servers for CMS-Type Subversion in the CMS section of PKitConfig.xml.
	*  Ensure no files are checked out in Stages for the legacy SVN profiles at the time of migration. To create a list of currently checked out SVN files execute the following commands on the Stages server in a shell with administrative permissions.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion_profile?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Create a New CMS Profile</title>
        <link>https://doc.stagesasaservice.com/261/subversion_profile?rev=1773421097&amp;do=diff</link>
        <description>Subversion Integration

Create a New CMS Profile

	*  Entering a Name for a CMS profile is optional. When a name is specified it will be displayed in forms where a document/file is associated with a CMS profile.
	*  It is required to select a Subversion Host (corresponds to a cms-host as defined in PKitConfig.xml).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/subversion?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Integrate with Subversion</title>
        <link>https://doc.stagesasaservice.com/261/subversion?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Integrate with Subversion

	*   Stages CMS Configuration
			*  Global Configuration Properties
			*  Host Sections
			*  Host-Specific Configuration Properties

	*  Create a New CMS Profile
	*  Migration of Legacy SVN CMS Profiles
	*  Known Limitations</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/system_requirements_mysql?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>MySQL Requirements</title>
        <link>https://doc.stagesasaservice.com/261/system_requirements_mysql?rev=1773421097&amp;do=diff</link>
        <description>MySQL Requirements

Native MySQL installation

Stages supports 8.0 and 8.4 Community Edition.

The following settings are highly recommended:


character-set-server=utf8
max_allowed_packet=500M
innodb_lock_wait_timeout=7200
transaction-isolation=READ-COMMITTED
lower_case_table_names=1
sql-mode = &quot;STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION&quot;
default-time-zone=&quot;+00:00&quot;</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/system_requirements_oracle?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Oracle Requirements</title>
        <link>https://doc.stagesasaservice.com/261/system_requirements_oracle?rev=1773421097&amp;do=diff</link>
        <description>Oracle Requirements

Stages supports the following Oracle versions:

	*  19c

Stages requires a separate tablespace on the Oracle server.

To access Oracle with Stages a technical/proxy user with at least the following permissions is necessary:

	*  CREATE SESSION</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/system_requirements?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>System Requirements for Stages 7.12</title>
        <link>https://doc.stagesasaservice.com/261/system_requirements?rev=1773421097&amp;do=diff</link>
        <description>System Requirements for Stages 7.12

Client Requirements

Stages is a web application, so a recent web browser is required on the clients.
 Browser  Supported Versions  Google Chrome  Latest Version  Microsoft Edge  Latest Version  Mozilla Firefox  Latest Version</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/tailor_process?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Tailor a Process</title>
        <link>https://doc.stagesasaservice.com/261/tailor_process?rev=1773421097&amp;do=diff</link>
        <description>Tailor a Process

Engineering processes typically differ from project to project. Process tailoring is one way to adjust a standard process to the different requirements of each project or program. Stages provides two levels of tailoring: using the tailoring rules that are modeled into the processes and manually adjusting the processes for situations not covered by the tailoring rules.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/tailor?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Tailor a process</title>
        <link>https://doc.stagesasaservice.com/261/tailor?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Tailor a process

There is no process model that is valid for all processes. All processes are based on the Metamodel but need to be tailored to fit certain requirements.

Ex. The metamodel for a car stays the same but there can be multiple tailored processes. The tailored processes for a gas, electric, and diesel car will be different. Rather than including all of the different safety processes for each and having to pick and choose which ones need to be completed, a tailored proce…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/tailoring_definition?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Tailoring</title>
        <link>https://doc.stagesasaservice.com/261/tailoring_definition?rev=1773421097&amp;do=diff</link>
        <description>Manage Tailoring

One of the most important aspects of product development processes is variance. No two products were ever developed with exactly the same process. Processes always vary, based on target customers, technology, available budgets, market regulations, and many more characteristics.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/tailoring?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage tailoring</title>
        <link>https://doc.stagesasaservice.com/261/tailoring?rev=1773421097&amp;do=diff</link>
        <description>Stages V7.2

Manage tailoring

(not in the software yet, for now, just talk about it and give background)

Tailoring

We use tailoring to incorporate requirements of project- or program-specific instances in a process. The specific requirements are tailored in/out of a process depending on the specifications of that process. The user viewing the tailored process will only see the relevant information for their project, not the tailored out information.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/teams?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Teams with Roles</title>
        <link>https://doc.stagesasaservice.com/261/teams?rev=1773421097&amp;do=diff</link>
        <description>Use Teams with Roles

Modeling of roles and teams through RASIC (Responsible, Approves, Supports, Informed, Consulted) allows a clear assignment to an activity or a workflow.

A direct assignment of an activity or a workflow to a role identifies the expectations for that role. An indirect assignment to a role happens through a team.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/understand?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Understand Process Content</title>
        <link>https://doc.stagesasaservice.com/261/understand?rev=1773421097&amp;do=diff</link>
        <description>Understand Process Content

Process content in Stages is normally structured by separating the different dimensions of WHAT, WHO, WHEN, HOW, and WHY.

	*  WHAT should be done: Activities  and Work Products
	*  WHO does it: Roles
	*  WHEN does it have to be done:</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_72_73?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Upgrade Stages 7.2 to 7.3</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_72_73?rev=1773421097&amp;do=diff</link>
        <description>Upgrade Stages 7.2 to 7.3

Mandatory manual actions

	*  After upgrading to Stages 7.3 edit file “server.xml”
			*  Windows: open file “\stages\conf\server.xml”
			*  Linux:  open file “/stages/conf/server.xml”

	*  Replace section &lt;Context path=</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_75?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Steps to upgrade from V7.5 to V7.6</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_75?rev=1773421097&amp;do=diff</link>
        <description>Steps to upgrade from V7.5 to V7.6

General Recommendations Before Upgrading

To be safe in case of any crashes/problems during the update, back up your database (dump) befor the upgrade.

On Linux servers where Stages was started with “stages start</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_76?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Steps to upgrade from V7.6 to V7.7</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_76?rev=1773421097&amp;do=diff</link>
        <description>Steps to upgrade from V7.6 to V7.7

General Recommendations Before Upgrading

To be safe in case of any crashes/problems during the update, back up your database (dump) befor the upgrade.

Stop Stages

Linux: execute sudo stages stop

Windows: stop the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_77?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Steps to upgrade from V7.7 to V7.8</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_77?rev=1773421097&amp;do=diff</link>
        <description>Steps to upgrade from V7.7 to V7.8

Check Security Settings

Stages 7.8 increases security by enforcing more robust security policies, e.g. disabling the access by users with Internet Explorer browsers by default. Other security settings have also been tightened.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_78?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Steps to upgrade from V7.8 to V7.9</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_78?rev=1773421097&amp;do=diff</link>
        <description>Steps to upgrade from V7.8 to V7.9

General Recommendations Before Upgrading

To be safe in case of any problems during the update, back up your database before the upgrade.

Stop Stages

Linux: execute sudo stages stop

Windows: stop the Stages and</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_79?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Steps to upgrade from V7.9 to V7.10</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_79?rev=1773421097&amp;do=diff</link>
        <description>Steps to upgrade from V7.9 to V7.10

Mandatory Manual Actions Before Upgrading

To be safe in case of any problems during the update, back up your database and the stages folder before the upgrade.

If the backup is running automated - please check whether the backup was created successfully.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_711?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Steps to upgrade from V7.11 to V7.12</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_711?rev=1773421097&amp;do=diff</link>
        <description>Steps to upgrade from V7.11 to V7.12

Create Backups Before Upgrading

To be safe in case of any problems during the update, back up your database and the stages folder before the upgrade.
If the backup is running automated - please check whether the backup was created successfully.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_from_712?rev=1776861332&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-22T12:35:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>How to upgrade to version 26.1</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_from_712?rev=1776861332&amp;do=diff</link>
        <description>How to upgrade to version 26.1

Version 26.1 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.

Please contact our customer care team to request an upgrade of your Stages Managed Service instance.

If you use a customized metamodel on your Stages Managed Service instance, it needs to be adapted to v26 by your Stages product consultant first.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_java?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Upgrade Java for Stages</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_java?rev=1773421097&amp;do=diff</link>
        <description>Upgrade Java for Stages



If you need to upgrade your Java version please proceed as follows:

	*  Backup the cacerts file from the location of the existing JDK …/jdk_&lt;old&gt;/jre/lib/security/  or create a new cacerts file including the necessary certificates (e.g. company root certificate).</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_to_7_10_5?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Upgrade to release 7.10.5.0 or higher</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_to_7_10_5?rev=1773421097&amp;do=diff</link>
        <description>Upgrade to release 7.10.5.0 or higher

With this release we simplify the initial setup of Stages for production and follow a security by default approach.
Therefore the default configuration for new Stages installations is prepared for HTTPS only access to Stages. For existing installation - after the upgrade to Stages 7.10.5.0 or higher - a few manual steps are necessary as outlined below.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/upgrade_troubleshooting?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>java.sql.SQLException: ORA-30036: unable to extend segment by [size] in undo tablespace [tablespace name]</title>
        <link>https://doc.stagesasaservice.com/261/upgrade_troubleshooting?rev=1773421097&amp;do=diff</link>
        <description>On upgrading Stages to newer versions there are many steps executed to modify the database. Below you&#039;ll find a variety of possible problems depending on your databse configuration and size.

java.sql.SQLException: ORA-30036: unable to extend segment by [size] in undo tablespace [tablespace name]</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/use_reports?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Reports</title>
        <link>https://doc.stagesasaservice.com/261/use_reports?rev=1773421097&amp;do=diff</link>
        <description>Use Reports

Stages contains a report engine that provides access to all process and project data managed in Stages.

Typical reports are:

	*  Reports that analyze the modeled process
	*  Reports that analyze the content of projects
	*  Administrative reports that analyze the usage of Stages</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/usecopy?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Copy</title>
        <link>https://doc.stagesasaservice.com/261/usecopy?rev=1773421097&amp;do=diff</link>
        <description>Use Copy</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/useprocessmodules?rev=1777291457&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-27T12:04:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Use Process Modules</title>
        <link>https://doc.stagesasaservice.com/261/useprocessmodules?rev=1777291457&amp;do=diff</link>
        <description>Use Process Modules

In Stages, a process modeled in a workspace of the type process module can be inherited into other workspaces. The content of a process module is dictated by the process architecture. A process module will contain generic process(es) to be inherited into an integrated standard process or even into an instance of a program or project.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/user_groups_permissions_scim?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>SCIM provisioning</title>
        <link>https://doc.stagesasaservice.com/261/user_groups_permissions_scim?rev=1773421097&amp;do=diff</link>
        <description>SCIM provisioning

SCIM, or System for Cross-domain Identity Management, is an open standard for the provisioning and deprovisioning of users and user groups to enterprise applications. It is able to significantly simplify the rollout of users and their permission group assignments in Stages.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/users_groups_permissions?rev=1776337486&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-04-16T11:04:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Users, Groups, and Permissions</title>
        <link>https://doc.stagesasaservice.com/261/users_groups_permissions?rev=1776337486&amp;do=diff</link>
        <description>Manage Users, Groups, and Permissions

In version 7.12, the following permission domains have been added:

	*  AI Administration: allow users to edit the AI prompts and Chatbot Views. (This replaces the AI Prompts domain from 7.11)
	*  Chatbot: allow users to use the Chatbot</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/versions?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Process Versions</title>
        <link>https://doc.stagesasaservice.com/261/versions?rev=1773421097&amp;do=diff</link>
        <description>Manage Process Versions

Stages processes can be baselined by using the process version feature. A modeler will always be making changes in the working version of the process, while the end users will typically only be shown the baselined valid process version.

Create a new version

To create a new process verisons, navigate to Management &gt; Process version and click or tap on the</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/visualizations-troubleshooting?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Problems with process visualizations</title>
        <link>https://doc.stagesasaservice.com/261/visualizations-troubleshooting?rev=1773421097&amp;do=diff</link>
        <description>Problems with process visualizations

Layout is not correct for shapes with non-latin characters (e.g. Korean)

Please import this test process into a new, empty workspace and check stages.log (follow the instructions on the process start page)

A warning for your language in the log file means that your configured diagram font does not support text in this language. A replacement font is used for text layout in this case, which means that the shape text may not be centered correctly (for exampl…</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/work_with_files?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Work with files</title>
        <link>https://doc.stagesasaservice.com/261/work_with_files?rev=1773421097&amp;do=diff</link>
        <description>Work with files

Stages supports you in your daily work, not only by providing process descriptions, but also by enabling you to gain rapid access to files. Via the Stages CM interface, it is possible to create, change and delete files.

Create a file in Stages</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/workspace_collections?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Workspace Collections</title>
        <link>https://doc.stagesasaservice.com/261/workspace_collections?rev=1773421097&amp;do=diff</link>
        <description>Manage Workspace Collections

To manage complex process landscapes with many process owners, the processes should be modeled in separate process modules and then integrated into larger entities. Those process modules should have defined interfaces, e.g. via work products or roles.</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/workspaces?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Manage Workspaces</title>
        <link>https://doc.stagesasaservice.com/261/workspaces?rev=1773421097&amp;do=diff</link>
        <description>Manage Workspaces

Manage the Workspace Tree

Go to Administration &gt; Workspaces.

With the respective menus you can create, delete, edit, and move workspaces.

The Open menu brings you to the workspace&#039;s process starting page.

Use Workspace Attributes</description>
    </item>
    <item rdf:about="https://doc.stagesasaservice.com/261/workwithfiles?rev=1773421097&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-13T16:58:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Work with files</title>
        <link>https://doc.stagesasaservice.com/261/workwithfiles?rev=1773421097&amp;do=diff</link>
        <description>Work with files

In an instantiated project or a program, specific deliverables are consumed as well generated during the execution of an activity. These deliverables or files are instances of the work product, which has further information like description</description>
    </item>
</rdf:RDF>
