Skip to content

Commit bb3791d

Browse files
ziyuheheziyuhehe
andauthored
Update (#29)
Co-authored-by: ziyuhehe <[email protected]>
1 parent e918b9f commit bb3791d

File tree

51 files changed

+887
-206
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

51 files changed

+887
-206
lines changed

CONTRIBUTING.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
- [Open a pull request](#open-a-pull-request)
1111
- [Submit your PR & get it reviewed](#submit-your-pr--get-it-reviewed)
1212
- [Your PR is merged](#your-pr-is-merged)
13-
- [Keep contributing as you use MicroStrategy Docs](#keep-contributing-as-you-use-microstrategy-docs)
13+
- [Keep contributing as you use Strategy Docs](#keep-contributing-as-you-use-strategy-docs)
1414

1515
## Getting started
1616

@@ -21,7 +21,7 @@ Before you begin:
2121

2222
### Use the 'Edit' button
2323

24-
Navigating a new codebase can be challenging, so we're making that a little easier. As you're using this MicroStrategy Embedding SDK Docs, you may come across an article that you want to make an update to. You can find and click the **Edit** button on the top right corner on that article, which will take you to the file in this repo where you'll make your changes.
24+
Navigating a new codebase can be challenging, so we're making that a little easier. As you're using this Strategy Embedding SDK Docs, you may come across an article that you want to make an update to. You can find and click the **Edit** button on the top right corner on that article, which will take you to the file in this repo where you'll make your changes.
2525

2626
Before you make your changes, check to see if an [issue exists](https://github.com/MicroStrategy/embedding-sdk-docs/issues) already for the change you want to make.
2727

@@ -44,7 +44,7 @@ Fork using GitHub Desktop:
4444

4545
### Make your update
4646

47-
Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-microstrategyembedding-sdk-docs-repository).
47+
Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-strategyembedding-sdk-docs-repository).
4848

4949
- Are you making changes to the application code? You'll need **Node.js v16** to run the site locally. See [contributing/development.md](contributing/development.md).
5050
- Are you contributing to markdown? We use [Markdown](https://www.markdownguide.org/basic-syntax/).
@@ -60,13 +60,13 @@ When you're done making changes and you'd like to propose them for review, use t
6060

6161
### Your PR is merged
6262

63-
Congratulations! The whole MicroStrategy community thanks you. :sparkles:
63+
Congratulations! The whole Strategy community thanks you. :sparkles:
6464

6565
Once your PR is merged, you will be proudly listed as a contributor in the [contributor chart](https://github.com/MicroStrategy/embedding-sdk-docs/graphs/contributors) and at the bottom of the page you contributed to.
6666

67-
### Keep contributing as you use MicroStrategy Docs
67+
### Keep contributing as you use Strategy Docs
6868

69-
Now that you're a part of the MicroStrategy Docs community, you can keep participating in many ways.
69+
Now that you're a part of the Strategy Docs community, you can keep participating in many ways.
7070

7171
**Learn more about contributing:**
7272

@@ -77,7 +77,7 @@ Now that you're a part of the MicroStrategy Docs community, you can keep partici
7777
- [:earth_asia: Translations](#earth_asia-translations)
7878
- [Starting with an issue](#starting-with-an-issue)
7979
- [Opening a pull request](#opening-a-pull-request)
80-
- [Working in the MicroStrategy/embedding-sdk-docs repository](#working-in-the-microstrategyembedding-sdk-docs-repository)
80+
- [Working in the Strategy/embedding-sdk-docs repository](#working-in-the-strategyembedding-sdk-docs-repository)
8181
- [Reviewing](#reviewing)
8282
- [Self review](#self-review)
8383
- [Test it locally](#test-it-locally)
@@ -87,7 +87,7 @@ Now that you're a part of the MicroStrategy Docs community, you can keep partici
8787

8888
## :memo: Types of contributions
8989

90-
You can contribute to the MicroStrategy Embedding SDK Docs content and site in several ways. This repo is a place to discuss and collaborate on MicroStrategy Embedding SDK Docs! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
90+
You can contribute to the Strategy Embedding SDK Docs content and site in several ways. This repo is a place to discuss and collaborate on Strategy Embedding SDK Docs! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
9191

9292
### :beetle: Issues
9393

@@ -101,7 +101,7 @@ When we merge those changes, they should be deployed to the live site within 24
101101

102102
### :question: Support
103103

104-
We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with MicroStrategy, unrelated to our documentation, please [contact MicroStrategy Support directly](https://www.microstrategy.com/support). Any issues, or pull requests opened here requesting support will be given information about how to contact MicroStrategy Support, then closed and locked.
104+
We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with Strategy, unrelated to our documentation, please [contact Strategy Support directly](https://www.microstrategy.com/support). Any issues, or pull requests opened here requesting support will be given information about how to contact Strategy Support, then closed and locked.
105105

106106
### :earth_asia: Translations
107107

@@ -117,16 +117,16 @@ You can browse existing issues to find something that needs help!
117117

118118
You can use the GitHub user interface :pencil2: for some small changes, like fixing a typo or updating a readme. You can also fork the repo and then clone it locally, to view changes and run your tests on your machine.
119119

120-
## Working in the MicroStrategy/embedding-sdk-docs repository
120+
## Working in the Strategy/embedding-sdk-docs repository
121121

122122
Here's some information that might be helpful while working on a Docs PR:
123123

124124
- [Development](contributing/development.md) - This short guide describes how to get this app running on your local machine.
125-
- [Content style guide for MicroStrategy Docs](contributing/content-style-guide.md) - This guide covers information about how we style our content and images. It also links to the resources we use for general style guidelines.
125+
- [Content style guide for Strategy Docs](contributing/content-style-guide.md) - This guide covers information about how we style our content and images. It also links to the resources we use for general style guidelines.
126126

127127
## Reviewing
128128

129-
We (usually the docs team, but sometimes MicroStrategy product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use MicroStrategy.
129+
We (usually the docs team, but sometimes Strategy product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use Strategy.
130130

131131
:yellow_heart: Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
132132

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,6 @@ If you have a solution to one of the open issues, you will need to fork the repo
5353

5454
#### And that's it
5555

56-
That's how you can get started easily as a member of the MicroStrategy Embedding SDK Documentation community. :sparkles:
56+
That's how you can get started easily as a member of the Strategy Embedding SDK Documentation community. :sparkles:
5757

5858
If you want to know more, or you're making a more complex contribution, check out [Getting Started with Contributing](CONTRIBUTING.md).

contributing/content-style-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ The list below shows the usage of emojis in our Docs site:
138138

139139
- Titles, sidebar labels, and headers
140140

141-
- These should use **sentence case**. For example, prefer "This is the title from MicroStrategy" over "This Is The Title From MicroStrategy".
141+
- These should use **sentence case**. For example, prefer "This is the title from Strategy" over "This Is The Title From Strategy".
142142
- `sidebar_label` should only be used if you want a different title in the sidebar than the `title` in front matter. (Note: For folders, `label` in sidebars.js takes priority over `sidebar_label`)
143143

144144
## Tables

docs/add-functionality/add-event.md

Lines changed: 39 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Once you have used the `dossier.create(props)` method to embed a dashboard into
1515

1616
## Events
1717

18-
Each supported event is described in the table below. You get the EventType from `microstrategy.dossier.EventType`.
18+
Each supported event is described in the table below. You get the EventType from `microstrategy.dossier.EventType` or `microstrategy.embeddingContexts.EventType`.
1919

2020
### onGraphicsSelected
2121

@@ -391,7 +391,8 @@ embedDossier.registerEventHandler(EventType.ON_LIBRARY_ITEM_SELECTED, libraryIte
391391
"projectId": "B19DEDCC11D4E0EFC000EB9495D0F44F",
392392
"name": "Distribution Center & Brands",
393393
"type": 55,
394-
"subtype": null
394+
"subtype": null,
395+
"isDocument": false
395396
}
396397
]
397398
```
@@ -570,6 +571,40 @@ embedDossier.registerEventHandler(EventType.ON_DOSSIER_INSTANCE_CHANGED, (conten
570571
}
571572
```
572573

574+
### onInstanceChanged
575+
576+
#### Event enumeration
577+
578+
`EventType.ON_INSTANCE_CHANGED`
579+
580+
#### Description
581+
582+
Raised when the a new object instance is created or destroyed. The object type could be a dashboard, document, report or bot.
583+
584+
#### Content
585+
586+
The event callback parameters contain the project id, object id, object type, object name, and the instance id.
587+
588+
#### Code example
589+
590+
```js
591+
embedDossier.registerEventHandler(EventType.ON_INSTANCE_CHANGED, (content) => {
592+
// Use the content here
593+
});
594+
```
595+
596+
#### Content example
597+
598+
```json
599+
{
600+
"projectId": "B19DEDCC11D4E0EFC000EB9495D0F44F",
601+
"objectId": "D9AB379D11EC92C1D9DC0080EFD415BB",
602+
"objectName": "Dashboard Prompted on Category",
603+
"objectType": "dossier",
604+
"instanceId": "EC003BC7A046E75DE83373A254824F20"
605+
}
606+
```
607+
573608
### onComponentSelectionChanged
574609

575610
#### Event enumeration
@@ -598,6 +633,8 @@ embedDossier.registerEventHandler(EventType.ON_COMPONENT_SELECTION_CHANGED, (con
598633
{
599634
"projectId": "B19DEDCC11D4E0EFC000EB9495D0F44F",
600635
"dossierId": "EC5441154009D3C39D5BD6AD75865EF4",
636+
"objectId": "EC5441154009D3C39D5BD6AD75865EF4",
637+
"objectType": "dossier",
601638
"selectedComponents": [
602639
{
603640
"key": "K52",

docs/add-functionality/add-functionality.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,11 +43,11 @@ Once you have embedded a dashboard, you can use helper methods in the Embedding
4343

4444
:::tip
4545

46-
If you plan to use Embedding SDK on a web page on a different domain from your MicroStrategy environment, please also meet the following requirements. More information in
46+
If you plan to use Embedding SDK on a web page on a different domain from your Strategy environment, please also meet the following requirements. More information in
4747

4848
1. [Enable Cross-Origin Resource Sharing (CORS)](../config.md)
4949
1. [Allow SameSite cookies](../config.md#allow-samesite-cookies)
5050

51-
If you plan to use Embedding SDK on the same domain as your MicroStrategy, the above changes are not required.
51+
If you plan to use Embedding SDK on the same domain as your Strategy, the above changes are not required.
5252

5353
:::

docs/add-functionality/authoring-library.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Author an embedded dashboard
33
description: To allow users to conveniently edit a dashboard, Embedding SDK allows embedding a dashboard in the authoring mode, whether it is during the initial load or in the view mode of the dashboard.
44
---
55

6-
Embedding MicroStrategy content within critical business applications empowers users to make smarter decisions by taking advantage of the dashboard development efforts that occur behind the scenes. To allow users to conveniently edit a dashboard, Embedding SDK allows embedding a dashboard in the authoring mode, whether it is during the initial load or in the view mode of the dashboard.
6+
Embedding Strategy content within critical business applications empowers users to make smarter decisions by taking advantage of the dashboard development efforts that occur behind the scenes. To allow users to conveniently edit a dashboard, Embedding SDK allows embedding a dashboard in the authoring mode, whether it is during the initial load or in the view mode of the dashboard.
77

88
:::tip
99

docs/add-functionality/error-handling.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
title: Error handling
3-
description: MicroStrategy provides custom error handling in two stages, during dashboard creation and after dashboard creation.
3+
description: Strategy provides custom error handling in two stages, during dashboard creation and after dashboard creation.
44
---
55

66
By default, Library displays a pop-up dialog when an error occurs, such as when a dataset is not found.
77

88
![library server error](../images/library_server_error.png)
99

10-
MicroStrategy provides custom error handling for these kinds of pop-up errors in two stages.
10+
Strategy provides custom error handling for these kinds of pop-up errors in two stages.
1111

12-
MicroStrategy also provides session error handling for session errors in two stages. Because the handling method of the session error is different from other errors, we don't use the custom error handling in this case.
12+
Strategy also provides session error handling for session errors in two stages. Because the handling method of the session error is different from other errors, we don't use the custom error handling in this case.
1313

1414
## Custom error handling
1515

@@ -67,11 +67,11 @@ microstrategy.dossier
6767
});
6868
```
6969

70-
### The overall MicroStrategy Library error behavior in embed case
70+
### The overall Library error behavior in embed case
7171

7272
The error generated by the embedded Library or dashboard page would output an error log in the browser console. Besides that,
7373

74-
- If `disableCustomErrorHandlerOnCreate` is set to `true` in `microstrategy.dossier.create` or `microstrategy.embeddingContexts.embedLibraryPage`, the custom error handler couldn't be registered. The error would only be shown by a popup error dialog, which is the same as the OOTB MicroStrategy Library behavior;
74+
- If `disableCustomErrorHandlerOnCreate` is set to `true` in `microstrategy.dossier.create` or `microstrategy.embeddingContexts.embedLibraryPage`, the custom error handler couldn't be registered. The error would only be shown by a popup error dialog, which is the same as the OOTB Library behavior;
7575
- If `disableCustomErrorHandlerOnCreate` is not set or is `false`:
7676
- If a custom error handler is set by `errorHandler` or `addCustomErrorHandler(customErrorHandler, false)`, the error would only invoke the custom error handler and wouldn't popup a Library error dialog.
7777
- If a custom error handler is set by `addCustomErrorHandler(customErrorHandler, true)`, the error would first popup an error dialog, and when the user clicks the button on the error dialog, the custom error handler would be invoked.
@@ -82,7 +82,7 @@ The error generated by the embedded Library or dashboard page would output an er
8282
When the session expiration error occurs:
8383

8484
- If there is no `sessionErrorHandler` defined, the page will show the Library's logout page.
85-
- If you define a `sessionErrorHandler`, the function will be executed. After 1 minute, the page will forcefully redirect to the OOTB MicroStrategy Library login page.
85+
- If you define a `sessionErrorHandler`, the function will be executed. After 1 minute, the page will forcefully redirect to the OOTB Library login page.
8686

8787
The differences from custom error handling:
8888

0 commit comments

Comments
 (0)