I am using Lotus Domino 9.0.1. I want integrate Domino with my application.Is there any API(method) for passing the iCal using Notes API.Usecase what i am trying is all the CRUD opertions on normal as well as Recurrence meeting.
There are at least two ways to create a calendar event from iCalendar input: 1) You can use the Notes Java back-end classes -- specifically the NotesCalendar.createEntry() method, or 2) You can use the REST calendar API -- specifically calendar events POST.
You can do all the other CRUD operations with both the back-end classes and REST. One advantage of REST is that it works "remotely". Your application doesn't need Notes or Domino installed locally to use the REST API. Based on your other questions on StackOverflow, I think you want to use the REST API.
Related
I have a hcl application to whose View I want to add entries from my local pc. I have very little knowledge about HCL in genral and have been looking for a soultion for days now without any success. Maybe Im looking at the wrong places but there was little to find. All I know right now is that I will probably end up sending my local data for the entries via postman and I do have to make an agent?/method that is accessable via browser that can receive these information and make entries with them.
I was just pushed into this thing. I wouldnt mind some usefull links to build my foundation as well.
There are many ways to add documents to a Notes/Domino database.
You are not very specific, it is not even clear if you want to do it programmatically. As Torsten said in his comment to your original post, there are many ways to do that.
Here are a couple:
Using the Notes rich client.
Through a web browser, accessing a web-enabled Domino database. This assumes the creator of the database has exposed the functionality to create documents on the web.
Use COM (or Java) to create the documents from an external scriptable application or using a programming language/platform supporting COM:
https://help.hcltechsw.com/dom_designer/9.0.1/appdev/H_EXAMPLES_ACCESSING_THE_DOMINO_OBJECTS_THROUGH_COM.html
Call a REST service on the Domino server that will create new documents. You can write a REST service using Lotusscript, Java or XPages:
https://www.slideshare.net/TexasSwede/break-out-of-the-box-part-2 (you can skip to slide 19)
Use Domino Access Services (DAS), a framework for adding REST services to Domino. A DAS service is implemented in Java and deployed as an OSGi plug-in:
https://ds-infolib.hcltechsw.com/ldd/ddwiki.nsf/dx/Create_your_own_Domino_REST_service_using_DAS
and
https://www.slideshare.net/JohnDalsgaard/engage-ug-rest-services-2015
Use node.js and the Domino AppDev Pack: https://doc.cwpcollaboration.com/appdevpack/docs/en/homepage.html
and
http://www.c3ug.ca/c3ug-blog/2020/6/30/announcement-learning-the-domino-appdev-pack-a-free-course-from-c3ug
There are probably a few more ways that I am forgetting...
Before you do anything else, you need to learn more about the Domino platform, the structure of a database, and the proper terminology used in Domino. If you don't understand the basics, you will not be able to write any kind of integration with Domino.
I'd like to create a set of recurring events but with a dynamic titles, e.g. for counting gym lessons... Is there a way to do this in Google calendar or is there a free or cheap alternative available?
This seems hard to do without scripting it via the Google Calendar API. You can set up the initial recurring event and then iterate over the sequence of other calendar events for that instance using the following endpoints:
Retrieve instances
Update event
I can't think of any other free services that assist with this off the top of my head.
If you'd like similar functionality across other calendaring systems including Outlook and Exchange without having to re-do the implementation with each of those APIs, you can also check out my company Kloudless's unified Calendar API (docs), which provides an abstraction layer for operations such as the ones above.
We're working with Cumulocity and we'd like to offer services to our customers that are not currently possible to implement with Cumulocity. As an example, we'd like to be able to retrieve a list of devices located within x kilometers of a given point.
Currently there are two limitations that prevent us from doing so:
the impossibility of extending the Cumulocity API with custom route/parameters
the impossibility of implementing custom functions for specific API GET calls
I can think of a workaround to achieve this, like a POST request of an event that would be processed by an Esper rule, generating another event/measurement that could then be accessed by a GET. But I think we can agree this is not a suitable mechanism.
Please not that the use case I described above is just an example. Our needs don't limit to this and we need a standardized way to expand our services without requirering updates on Cumulocity side.
There are two topics here, I believe:
Geo-querying: Some geographical querying and aggregation use cases can be handled through CEL. A general geo-querying API is on the Cumulocity roadmap. Note: This use case is not only related to extending the API, as such queries go right down into the database.
Extending the API: That is actually possible. Cumulocity has a microservices API in which you can expose other APIs under the URL /services/.... This is, for example, how connectivity platforms are interfaced. The API is not on the web site because it's not GA yet, but you can certainly discuss it with your Cumulocity contact or open a ticket. This btw includes also adding permissions for the new microservices, so that you can do proper A&A.
I would like to create my own web chatbot and i like to integrate my app with wit.ai for natural language classification.I need to know how to integrate wit.ai service(through api call) with my application(any language in backend).i am using C# in front end.I have gone through the integration part Which posted in wit.ai website.But i don't know how to connect it .Could anyone send me a integration details little briefly
I think the short answer is its similar to how you would call any other APIs from your application server components. Wit exposes multiple APIs like message, speech and converse which you can call by passing the Authorization token and other payloads and make use of the API response in your application.
You can use message API if you are only interested in extracting
intent and other atributes of the sententense
Use speech for building voice based application and
Converse if you want to build a little more smarter app. Currently you can only pass text for converse APIs.Hoping they will introduce voice option for this soon.
Now to make things simpler, they have also provided SDKs in various languages like node-wit, pywit etc. So if you want to build your server side logic using on nodejs or python you can use these SDKs. The advantage is that you dont have to manage raw APIs calls and instead it is all managed by SDK. Also, other big advantage is that you can make use of runActions method which encapsulates converse API and make things simpler. If you want to build in nodejs then the messenger example is a good starting point. You can borrow all this logic/concept in your app and replace FB related calls etc with your custom bot. For Python you can look at the below link
https://github.com/wit-ai/pywit/pull/55
Also, you can explore the options like using other frameworks like botkit if you plan to integrate wit with other chatbots like FB messenger or slackbot as these frameworks provide more flexibility and ability to easily switch to different chatbots in future. But they don't seem to properly support the converse API of wit.
You are specifically looking for integration details. Since you are using c# for frontend app, natuarally the best option would be to use c# for backend as well. In which case you will be left with directly calling wit APIs from your backend as I think there are no SDKs in c#. If you want to make use of SDK in node or python etc then you will have to build a rest based backend (for example) which can be invoked from your c# application. I am currently working on a nodejs app and integrating it with wit using node-wit. I can share some code once its ready but i dont know when I will be able to finish it. For bootstrapping my application I have used this node application. If you have some understanding of node then you can look at the /server/controllers logic. Similar to this application I have built a witController which uses runAction to interact with wit and I am calling this from front-end when user submits a message to your bot. The biggest challenge in runAction is to figure-out a way to send back the wit response to your front-end and get follow up response from user. Wit sends the response in Send method as you can see in the node-wit's messanger example.
Hope this helps!
Hi
I am currently working on an application which is implementing salesforce.com REST api. I have done all the authentication part and received all the info needed. Now I want my application to push the leads into the customer's account. But the lead fields can be customized and different customer use their different custom fields, so any1 can suggest me how to add that custom field in my form which will be pushed to the customer's salesforce account.
Thanks
You can use the describe resource in the REST API to obtain the metadata about the Load object, including all the fields.
https://{someinstance}.salesforce.com/services/data/v20.0/sobjects/lead/describe
You can use the list of fields to drive your form, and to control what you subsequently POST to /services/data/v20.0/sobjects/lead to create the new lead.
Here's the link to the REST API pilot docs incase you haven't seen them
No idea if the REST API supports describe() calls, they're a way of querying for all metadata about table (columns, their types etc). In normal webservice API this info can be found at http://www.salesforce.com/us/developer/docs/api/index_Left.htm#StartTopic=Content/sforce_api_calls_describesobject.htm#topic-title
the Metadata REST API was put on hold by Salesforce, so there is no REST API for Metadata (there is some limited support in the Tooling REST API, but not enough to create an object).
https://salesforce.stackexchange.com/questions/20763/creating-a-custom-object-using-rest-api