Продовец и вич

Reference: Manifest schema for Microsoft Teams

Note

For help on migrating your v0.4 manifest to v1.x, see our migration guide.

The Microsoft Teams manifest describes how the app integrates into the Microsoft Teams product. Your manifest must conform to the schema hosted at. Versions 1.0 and 1.1 are also supported.

The following schema sample shows all extensibility options.

Sample full schema

The schema defines the following properties:

$schema

Optional, but recommended – String

The URL referencing the JSON Schema for the manifest.

Tip

Specify the schema at the beginning of your manifest to enable IntelliSense or similar support from your code editor:

manifestVersion

Required – String

The version of the manifest schema this manifest is using.

It should be "1.2".

version

Required – String

The version of the specific app.

If you update something in your manifest, the version must be incremented as well. This way, when the new manifest is installed, it will overwrite the existing one and the user will get the new functionality. If this app was submitted to the store, the new manifest will have to be re-submitted and re-validated.

Then, users of продовец и вич app will get the new updated manifest automatically in a few hours, after it is approved.

If the app requested permissions change, users will be prompted to upgrade and re-consent to the app.

This version string must follow the semver standard (MAJOR.MINOR.PATH).

id

Required – Microsoft app ID

The unique Microsoft-generated identifier for this app.

If you have registered a bot via the Microsoft Bot Framework, or your tab's web app already signs in with Microsoft, you should already have an ID and should enter it here. Otherwise, you should generate a new ID at the Microsoft Application Registration Portal (My Applications), enter it here, and then reuse it when you add a bot.

packageName

Required – String

A unique identifier for this app in reverse domain notation; for example, com.example.myapp.

developer

Required

Specifies information about your company.

For apps submitted to AppSource (formerly Office Store), these values must match the information in your AppSource entry.

NameMaximum sizeRequiredDescription
32 charactersThe display name for the developer.
2048 charactersThe URL to the developer's website. This link should take users to your company or product-specific landing page.
2048 charactersThe URL to the developer's privacy policy.
2048 charactersThe URL to the developer's terms of use.

name

Required

The name of your app experience, displayed to users in the Teams experience.

For apps submitted to AppSource, these values must match the information in your AppSource entry.

NameMaximum sizeRequiredDescription
30 charactersThe short display name for the app.
100 charactersThe full name of the app, used if the full app name exceeds 30 characters.

description

Required

Describes your app to users.

For apps submitted to AppSource, these values must match the information in your AppSource entry.

Ensure that your description accurately describes your experience and provides information to help potential customers understand what your experience does.

You should also note, in the full description, if an external account is required for use.

NameMaximum sizeRequiredDescription
80 charactersA short description of your app experience, used when space is limited.
4000 charactersThe full description of your app.

Important

We currently have an продовец и вич with full descriptions longer than 256 characters.

You can use a longer description in your Seller Dashboard app submission.

icons

Required

Icons used within the Teams app. The icon files must be included as part of the upload package. See Icons for more information.

NameMaximum sizeRequiredDescription
2048 charactersA relative file path to a transparent 32x32 PNG outline icon.
2048 charactersA relative file path to a full color 192x192 PNG icon.

accentColor

Required – String

A color to use in conjunction with and as a background for your outline icons.

The value must be a valid HTML color code starting with '#', for example .

configurableTabs

Optional

Used when your продовец и вич experience has a team channel tab experience that requires extra configuration before it is added.

Configurable tabs are supported only in the teams scope, and currently only one tab per app is supported.

The object is an array with all elements of the type. This block is required only for solutions that provide a configurable channel tab solution.

NameTypeMaximum sizeRequiredDescription
String2048 charactersThe URL to use when configuring the tab.
BooleanA value indicating whether an instance of the tab's configuration can be updated by the user after creation.

Default:

Array of enum1Currently, configurable tabs support only the scope, which means it can be provisioned only to a channel.

staticTabs

Optional

Defines a продовец и вич of tabs that can be "pinned" by default, without the user adding them manually.

Static tabs declared in scope are always pinned to the app's personal experience. Static tabs declared in the scope are currently not supported.

The object is an array (maximum of 16 elements) with all elements of the type.

This block is required продовец и вич for solutions that provide a static tab solution.

NameTypeMaximum sizeRequiredDescription
String64 charactersA unique identifier for the продовец и вич that the tab displays.
String128 charactersThe display name of the tab in the channel interface.
String2048 charactersThe URL that points to the entity UI to be displayed in the Продовец и вич canvas.

Must be HTTPS.

String2048 charactersThe URL to point at if a user opts to view in a browser.
Array of enum1Currently, static tabs support only the scope, which means it can be provisioned only as part of the personal experience.

bots

Optional

Defines a bot solution, along with optional information such as default command properties.

The object is an array (maximum of only 1 element—currently only one bot is allowed per app) with all elements of the type.

This block is required only for solutions that provide a bot experience.

NameTypeMaximum sizeRequiredDescription
String64 charactersThe unique Microsoft app ID for the bot as registered with the Bot Framework.

This may well be the same as the overall app ID.

BooleanDescribes whether or not the bot utilizes a user hint to add the bot to a specific продовец и вич. Default:
BooleanIndicates whether a bot is a one-way, notification-only bot, as opposed to a conversational bot. Default:
Array of enum2Specifies whether the bot offers an experience in the context of a channel in aor an experience scoped to an individual user alone ().

These options are non-exclusive.

bots: commandLists

An optional list продовец и вич commands that your bot can recommend to продовец и вич. The object is an array (maximum of 2 elements) with all elements продовец и вич type ; you must продовец и вич a separate command list for each scope that your bot supports.

See Bot menus for more information.

NameTypeMaximum sizeRequiredDescription
array of enum2Specifies the scope for which the command list is valid.
array of objects10An array of commands the bot продовец и вич the bot command name (string, 32)
: a simple description or example of the command syntax and its argument (string, 128)

connectors

Optional

The block defines an Office 365 Connector for the app.

The object is an array (maximum of 1 element) with all elements of type.

This block продовец и вич required only for solutions that provide a Connector.

NameTypeMaximum sizeRequiredDescription
String64 charactersA unique identifier for the Connector that matches its ID in the Connectors Developer Portal.
Array of enum1Specifies whether the Connector offers an продовец и вич in the context of a продовец и вич in aor an experience scoped to an individual user alone продовец и вич.

Currently, only the scope is supported.

composeExtensions

Optional

Defines a messaging extension for the app.

Note

The name of the feature was changed from "compose extension" to "messaging extension" in November, 2017, but the manifest name remains the same so that existing extensions continue to function.

The object is an array (maximum of 1 element) with all elements of type продовец и вич.

продовец и вич

This block is required only for solutions that provide a messaging extension.

NameTypeMaximum SizeRequiredDescription
String64The unique Microsoft app ID for the bot that backs the messaging extension, as registered with the Bot Framework.

This may well be the same as the overall app ID.

BooleanA value indicating whether the configuration of a messaging extension can be updated by the user. The default is .
Array of object1Array of commands the messaging extension supports

composeExtensions.commands

Your messaging extension should declare one or продовец и вич commands.

Each command appears in Microsoft Teams as a potential interaction from the UI-based entry point.

Each command item is an object with the following structure:

NameTypeMaximum sizeRequiredDescription
String64 charactersThe ID for the command
String32 charactersThe user-friendly command name
String128 charactersThe description that appears продовец и вич users to indicate the purpose of this command
BooleanA Boolean value that indicates whether the command should be run initially with no parameters.

Default:

Array of object5The list of parameters the command takes. Продовец и вич 1; maximum: 5
String64 charactersThe name of the parameter as it appears in the client.

This продовец и вич included in the user request.

String32 charactersUser-friendly title for the parameter.
String128 charactersUser-friendly string that describes this parameter’s purpose.

permissions

Optional

An array of which specifies which permissions the app requests, which lets end users know how the extension will perform.

продовец и вич

The following options are non-exclusive:

  •   Requires user identity information
  •   Requires permission to send direct messages to team members

validDomains

Optional, except Required for apps with tabs

A list of valid domains from which the extension expects to load any content.

Domain listings can include wildcards, for example. If your tab configuration or content UI needs to navigate to any other domain besides the one use for tab configuration, that domain must be продовец и вич here.

Important

Do not add domains that are outside your control, either directly or via wildcards. For продовец и вич, is valid, but is not valid.

The object is an array продовец и вич all elements of the type .

Источник: https://docs.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema

Copyright © 2018.