• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 1399 views
  • Users 0 members are here
Options
Related

Descripeinces Between Documentation and Code

Stephen Vicino

When looking at the documentation for the evolutionTagTextBox, found here: community.telligent.com/.../evolutiontagtextbox-jquery-plugin, it states the only option allowed is AllOptions. An array of tag options. However in the code for for Forums - Create/Edit Post, the default widget is passing in an object with an applicaitonId.

context.tagBox.evolutionTagTextBox({applicationId:context.applicationId});

Can the documentation please be updated to reflect all options of this function?

Thank you!

Parents
  • 0

    I've logged this to update documentation on all affected current versions:

    TE-19055: Update documentation for evolutionTagTextBox to reflect all plugin options

    Our documentation is generated from our source so this is a scheduled change (and not a direct edit to the documentation). That said, the other options available are:

    • applicationId (GUID as string): The content-model Application Identifier for the application context of tag selection. When set, tags are loaded for this application and the allTags option is ignored.
    • typeId (GUID as string): The variation or use-case for this tag set. TypeIds are used to differentiate usage of core services into subsets (for example, tags for "Location" vs tags for "Severity"). When not set, the default tag set will be used.
Reply
  • 0

    I've logged this to update documentation on all affected current versions:

    TE-19055: Update documentation for evolutionTagTextBox to reflect all plugin options

    Our documentation is generated from our source so this is a scheduled change (and not a direct edit to the documentation). That said, the other options available are:

    • applicationId (GUID as string): The content-model Application Identifier for the application context of tag selection. When set, tags are loaded for this application and the allTags option is ignored.
    • typeId (GUID as string): The variation or use-case for this tag set. TypeIds are used to differentiate usage of core services into subsets (for example, tags for "Location" vs tags for "Severity"). When not set, the default tag set will be used.
Children
No Data

About
Privacy Policy
Terms of use
Copyright 2024 Verint, Inc.
Powered by Verint Community