We are using the JavaScript API from within an Outlook addin to set and get roaming settings for the addin.
According to the article linked above, it is possible to set those settings using EWS. I have been unable to find any examples on how to do it. What is the right way to do that?
Yes and there are examples of doing so on the page you linked to eg https://learn.microsoft.com/en-us/javascript/api/outlook/office.roamingsettings?view=office-js
Yes as the above link states
They can be accessed by Exchange Web Services or Extended MAPI. They should not be used to store sensitive information such as user credentials or security tokens.
so you can write using EWS (or MAPI) to modify the underlying FAI item.
Related
I am looking for a way to change the language for a single user for the complete GSuite.
For Gmail for example it would be this. However I would like to change the default language for the complete GSuite.
Is that somehow possible?
Two things:
As an admin, you cannot change the GSuite language for already existing users, you can only set-up a language for new users as decribed here.
Unfortunately the implementation of the feature above (Account settings > Profile > Language) has not been implemented into the Admin SDK yet.
Indeed, multiple features available in the Admin console have not been implemented into the API (yet).
As for the language settings, currently it is not even possible to retrieve them via API, not to mention to change them.
Issue:
A Dashboard (created in SAP Dashboards) has URL Buttons set up with OpenDocument URLs as links.
When this ‘landing page dashboard’ is opened from the BI Launchpad (whether it’s saved as your default/home page or accessed directly from the platform file structure)… it requires additional authentication to follow an OpenDocument URL. Regardless of file type, Webi documents, or other dashboard files.
Not all users experience this issue, but at least ½ do. Need to understand the difference in behavior and the root cause of it to advise fix.
Referencing OpenDocument user session documentation, there are workarounds with tokens and serialized sessions, but what other settings come into play to explain that only half of the users are impacted and prompted when using native functionality from launchpad?
One possible reason for this behavior is that the domain of the BO server as displayed in the address bar of the browser is different from the domain in the openDocument link.
For example, after logging in to BI launch pad, the browser displays the following in the address bar:
http://bi4server.company.com/BOE/BI
but the openDocument link is:
http://bi4server/BOE/OpenDocument/opendoc.....
In this case, the domain is different so the original session isn't recognized. If this is the case, the easiest solution is to remove the protocol and domain values from the URL, so that it begins with:
/BOE/OpenDocument/opendoc.....
Is it possible to embed a SAP BO object into a HTML container? For instance, embed a dashboard into my page instead of opening a new tab redirecting to the BO.
If you use OpenDocument, and put that in an iframe in your HTML page, you should be able to embed the BusinessObjects content into your web page, provided the object type is supported by OpenDocument (e.g. WebI, Dashboards, …).
One thing to keep in mind is that the user will still need to authenticate to the BusinessObjects platform. Setting up SSO results in automatic authentication, thus not prompting your end-user. If SSO is not possible, there are ways to authenticate the user without prompting (e.g. setting up trusted authentication, using the SDK to retrieve a logon token in the background, etc).
OpenDocument manuals are available here. Just make sure to select the correct manual corresponding to your version of BusinessObjects, as the features tend to differ between versions.
I built some widgets and uploaded on my local marketplace, is there a way to share that?
And better is it possible to share a Mashup (the widget composition) without giving the
possibility to wiring to the user?
I mean the user should use an application layout without change anything.
You can make public your workspaces/dashboards following the steps documented in the user guide. Only the owner of a workspace will be able to modify it. I think this is what are you searching for.
Another option is to create a packaged mashup using the "Upload to my resources" option in the editor view:
Take a look to the "Advanced" tab, where you can block widgets (make them unremovable), block connections (make wiring connections unremovable) and embed used widgets/operator (by default packaged mashups depends on the user having installed all the required widgets/operators. This way you can distribute the widgets and operators used by the mashup in the same package).
However, take into account that this method is meant for sharing mashup templates, the user will always be able to add additional widgets and create new connections in the wiring view.
Once packaged, mashups/dashboards (and widgets and operators) can be uploaded to a WStore server (e.g. to the Store portal provided on FIWARE Lab) for sharing them with other users. The steps for making this is also described in the WireCloud's user guide.
I have the problem, revisited.
I have set up a working Marketplace instance (v2.3) but am unable to integrate it with Wirecloud. The marketplace is correctly registered but all the requests i am making to this Marketplace are throwing 502 error, even though i am actually able to see some results when querying the Marketplace server through a browser.
Indicatively, i can issue a GET command at http://:8080/FiwareMarketplace/v1/registration/stores/ and get an answer, but Wirecloud's internal APIs return a 502 (Bad Gateway).
Any idea on what might have gone wrong?
PS: This happens for WC v0.6.5. When upgrading to a newer (Beta) version of WC, everything seems to be performing as expected, i.e. the marketplace is correctly inserted and the stores are correctly retrieved and processed.
I reviewed the Box authentication documentation as well as the other StackOverflow questions but I'm still unable to find definite answer.
My client is an enterprise Box client and would like to build a company's internal web application that would login into Box.com using service/admin account and create folder and upload a file. The uploaded folder will be available to specific customer that will login into Box and upload additional files.
I created a sequence diagram to depict the same.
Would you let me know if this is a supported Box authentication model? Can the Box 2.0 Beta API Token be used to login as service account and create file/folder/share?
Thanks for your help!
There are several options that could work for you. Let me suggest the simplest one first, and if that is not sufficient, then I can suggest other ways to accomplish your goal.
You can use the regular Box authentication for your solution. To do so, simply get an API key and an auth-token for your application. Then, after you have uploaded your file, use the V2 API to create a shared link for your file. You can email that shared link to the client, and they can use the link to access the file.
there has been new developments since this question was posted, and now it's possible to use JWT (JSON Web Token) and Box Developers Edition to access Box.
If you create a developer account you will be able to create App users and login using an enterprise id and a private key file. Check out the docs for more information: Box Developer Edition
Additonally, boxsdk comes with support for Box Developer Edition