I've tried to find the answer but no luck. The Asana Developers blog has a post from Feb 2017 states the availability of the Boards API. See here:
https://asana.com/developers/feed/boards-api
But there are almost no details of how to use it. Can you please tell me how we can access board columns and whether or not a project is a Boards view project? Why is this so hidden?
Boards and list projects are very similar in the API. You access board columns using the sections endpoint: GET /projects/project-id/sections
You can determine if a project is a board or a list by querying the project: GET /projects/project-id. The JSON response will have a "layout" key with either a "board" or "list" value.
We are working on releasing more board specific documentation. We hope to have this clearly documented soon. In the meantime, you can use the sections docs for columns and projects docs for boards.
Related
We're starting a new development project using on-premise TFS 2018, git and Visual Studio. In the past we've followed the Agile model of creating epics and user stories and putting the requirements/ui mockups and other details directly in the user stories.
After living through that approach, we don't want go back down that road for the following reasons:
1) Once that feature is shipped, it becomes extremely difficult to locate the info. Who remembers what feature was done in what user story?
2) No centralized place to store feature documentation. Of course, we all don't want take the waterfall approach of spending 2 years writing feature requirements, but there is something to be said of having a centralized place organized by feature area that contains the relevant documentation.
3) Have you ever tried to read an extensive user story with requirements acceptance testing through either the web interface or through Visual Studio? It gets old pretty fast having to read through a 8 line window.
What we would like to do is do a hybrid of documentation and reference a link to the doc in the user story. The user story exists for sprint tracking, but the details are stored in the document. After the feature/user story has shipped, we can refer to the doc.
Therefore the question becomes how to store this type of info in TFS and link to it so it can open with a link in the user story. We know we can do this with SharePoint, but is it possible to do in on-premise TFS?
Currently, this is not directly possible in TFS with outgoing with some 3rd party vendors like Modernrequirements which will be paid services.
You could always use the CMMI template which is used for creating and managing requirement Workitems, but not for storing a huge set of requirements as you typically stored in requirement documents.
As you mentioned there are other ways like Storing the documents in
SharePoint, one drive etc., and link to the user stories
Creating a
markdown
in the user stories itself.
Check-in those documents in the version control(Git,TFVS)
Refer to this similar SO in order to understand it better.
After initial browsing in Google, I couldn't work out the scope of DocuSign API.
I would like to know if it's feasible to implement these features
Multiple templates with custom form fields
Assign workflow to templates - multi-user e-signing by stages?
automate e-signing internally
User management/privileges - to create new document, recall/cancel, etc
Manage List of recipients - type association
Reporting such as; number of documents signed in the last month,
Please briefly explain what is DocuSign capable of and what needs to be developed differently
Thanks in advance
The general answer to your question is "yes." The DocuSign website, Developer Center, and Signature API reference documentation can help you understand the DocuSign Signature product and APIs.
If you have additional questions, you can talk with DocuSign staff, or try it for yourself. The Developer center enables you to create a free developer sandbox.
For API issues, you can also ask questions here on StackOverflow. Note that your questions should be much more specific than the questions you listed above. You also should show what you have already tried and what is not working for you.
I am trying to use "Flow" to automate emails every time a new item is added to a SharePoint discussion board.
This is working fine with all lists, however, it does not do anything when I create a flow for the discussion board. The name of the discussion board does not even come up as an option in the "List" category and if I use the "Documents" option instead of the lists, I am able to choose the correct discussion board, but the alerts do not work.
Discussions are based on the folder content type, with each reply to a parent discussion being an item within that folder.
Flow does not currently support many triggers or operations against folders (including discussion boards) in SharePoint sites, though they've been steadily adding functionality since Flow was introduced.
It's possible that this functionality will be added in the future. You can make suggestions and vote on proposed functionality in Microsoft's "Flow Ideas" community.
In my "Articles" resource in the manager I have a table that shows all my posts. There I see: publish date/Post Title/Author/Comments and Tags.
I wish to have also a specific template variable to be displayed into this table.
Do you know, if there is a way to do that?
(I am happy for every hint, because "Articles" doesn't offer categories,so I need to create this option by template variables.)
By the way, do you know why there is no active forum for ModX questions? It is very difficult to get feedback or help for this content management system.
First of all, articles is discontinued. I just setup a blog and I used collections for it.
Next: forums.modx.com is a good place, twitter is fast if you add the #MODX hashtag to your question. Best option: Link on twitter to your question in MODX forums :)
Now on your main question: there is no option in articles to modify the view in the backend. If you use collections, it's easy and even described in the official docs: https://rtfm.modx.com/extras/revo/collections
As you can see on the image, you can have images (and all kind of TVs) in the overview. Collections can display all kind of TVs
As Articles and Collections is just another way to present resources inside the backend, it's 100% compatible. So you can change from articles to collections quite easily.
I would like to create a small Xpages application that can show the calendar of our conference room. My idea is to have a web browser open on the Conference Room TVs so when somebody wants to get in the conference room they will see really quick that there is a meeting scheduled in 10 min.
I have tried using this template from OpenNTF - Link but I couldn't figure out how to pull the data from my Conference room resource into the calendar.
Any other idea how I can accomplish this?
Note: Having the user check the conference room schedule on LN is not an option. They already don't like LN.
Thanks,
Extension Library has a calendar control. It's basically the (8.5) iNotes calendar control, so data is loaded via a REST service. There are two methods of getting the data into a REST service, depending on whether or not the view you're picking up has columns with the programmatic names that are found in a Notes Mail calendar. The documentation in the XPages Extension Library book should cover the basics but, if you need clarification on any of the content, I wrote it.
Modifying the look and feel is not likely to be easy, because it's an XPage version of an IBM-specific Dojo-based control, which is possibly also why no version has been released to use the R9 look and feel.
Alternatively, it would be feasible to build a repeat control layout. Creating a ViewEntryCollection based on a DateRange is key to getting all entries between dates.