Hi I want to use the Microsoft Graph - Outlook Task API in a production site - however its been in Beta for 2 years and the last update I found was it would be in the next release (this was dated 2017). Any news or updates about when this will be available to use.
Chad here from the Tasks team. Yep, it's been a while and we're working on it. I don't have anything we can announce at this point, but we'll let you know when it's ready.
Related
Currently I am working in a project where we have 8 instances accross different geographies. We currently use bmc rlm ( https://docs.bmc.com/docs/ReleaseLifecycleMgt/50 ) for deployment automation.
However to keep track of our deployment ids we are using excel.
Starting from Dev environment , to QA environment ( each region has
its own QA and schedule ) and ultimately move to Production.
What I wanted to know was , is there any tool that you use to keep
track of deployments ?
We tried using sharepoint but it is kind of limiting in the features.
We would ideally like a workflow to be created , whereby developers
submit the request with the dev deployment id.
Workflow goes to Release Approver for QA env. Once he/she approves ,
QA testing team gets notified.
Please let us know if anybody else faced this kind of issue and used some tools for the same?
We have recently started public preview of Reliza Hub https://relizahub.com which aims to solve this problem.
Some of the functionality you are asking (particularly approvals) is not there yet, but it's coming. Tracking functionality and mapping instance to releases is there already.
Currently I'm trying to add documentation as we go, so far Version Increment workflow is documented here. And functionality to send release data to Reliza Hub is documented in our client github.
Would be happy to provide support and discuss incomplete or missing features via our new reddit channel r/Reliza.
I wrote a QB integration a few years ago that uses the Web Connector to read and write data to and from QB desktop products. It works well but I am not in love with the Web Connector.
I am tasked with setting up another QB integration. I was hoping to avoid using the Web Connector this time. There are a few reasons why I am trying to avoid the Web Connector but the main reason is I would like to make this integration work with both Desktop and Online versions of QB.
Is it possible to use the Intuit Sync Manager to sync the company data up to Intuit and then just use the standard Online APIs to connect to that company file? I have done some testing and I can connect to QB Online via the Online APIs but I cannot seem to get it to see the synced company files.
Any help with this would be great. Just looking for a little direction here.
Thanks in advance for any help.
For QBO, of-course, you can use QBO REST APIs(V3) API.
Ref - https://developer.intuit.com/docs/0025_quickbooksapi
But for QBD, QBSDK and web-connector is still the only approach.
QBD V2 and V3 REST APIs are already deprecated.
https://developer.intuit.com/docs/0250_qb
https://developer.intuit.com/docs/0250_qb/0010_get_oriented/0080_quickbooks_web_connector
FAQ
Thanks
I'm using a twitter API to fetch latest tweets from some person.
It was working well until 16 June 2013.
But now it gives me error - "410 error - rest api v1 not active" while fetching tweets.
Can anyone please help me out to migrate api version 1.1 over 1.0?
or
any other solution
Thanks
I never worked with twitter http api directly. If your twitter codebase is small then you can refactor your code by using a library or implementing some kind of abstraction to make migration to later minor API changes less painful.
As I can see from this article migration seems pretty straightforward. You should always authenticate your requests for all API calls.
API v1 was retired recently, as outlined here. To get up and running again, look at the changes from 1.0 to 1.1 here or here.
I've started to read something about certain Twitter API 1.0 deprecation deadline around march 2013, inviting all their users to migrate onto the 1.1 version of said API. The main difference between the 2 of them (among others) seems to be "the OAUTH thing".
Currently, I've been developing an iOS/Android app, which uses the search.twitter.com/search.json API with no major issues.
The nice thing is that "search.twitter.com" API is an unauthenticated one, and for now, it's more than enough for my needs. I "don't currently want to invest time" onto the OAUTH authentication right now.
On the other hand, and to be honest, I have no idea if the "search.twitter.com" API is the same thing as the 1.0 Twitter API. Is it? Have I been using Twitter API 1.0 without knowing it?
Does anyone know for sure if the search.twitter.com "API" is going to become "also" deprecated on March 2013?
Thanks!!
Finally, it looks like this API will be deprecated.
You can find more information on Twitter developers forum.
https://dev.twitter.com/discussions/12727
https://dev.twitter.com/discussions/14587
https://dev.twitter.com/discussions/14785
So it's time to move 1.1 and OAuth.
We are moving from Mantis to JIRA and wish to keep Mantis alive for some time until the migration is complete and all the users are migrated.
All users (esp. the dev team) that have been migrated to JIRA shouldn't continue with Mantis (maybe deactivate accounts) and concentrate on JIRA alone.
Thus if a Mantis issue that was migrated to JIRA gets fixed/commented (in JIRA) the new status should be synchronized to the still existing Mantis issue.
And (if possible) new issues that are created in Mantis should be automatically be added to JIRA (if this is not possible then thats OK too)
Does anybody know of a tool or plugin that can do this?
I do not know any tool that does it, but in our company we have successfully implemented sync tool for Jira<->Footprints and Jira<->CRM. It would use Jira SOAP API (or REST starting from 5.0) and Mantis SOAP API. This tool can regularly check issues in both systems and update them accordingly.
Jira SOAP API - http://docs.atlassian.com/software/jira/docs/api/rpc-jira-plugin/latest/index.html?com/atlassian/jira/rpc/soap/JiraSoapService.html
Jira REST API - https://developer.atlassian.com/display/JIRADEV/JIRA+REST+APIs
you can implement your own sync using Jira's REST API as #Daria replied above, or you can use Task Adapter for manual data synchronization between Jira and Mantis.
Sorry I have no immediate answer, but we are developing an internal tool for exactly this purpose:
migrate existing issues from Mantis -> JIRA
ability to enter new issues in Mantis and have them synced to JIRA
activity in JIRA issues replicated back to Mantis
workflow disabled in Mantis (issues are slaved to JIRA state)
keep Mantis alive for N months while users are trained and migrated
It is using their SOAP and REST APis respectively.
If there is interest and it works well (looking really good at this stage) I will seek permission to open source it.