I'm working on a program which is kind of application launcher. It should suggest frequently-running apps and documents to users. For this purpose I'm looking for a API or a registry key documentation which could help me to get list of the recently opened documents with their apps.
For instance:
1. notepad.lnk:
a. readme.txt
b. manual.txt
2. calc.lnk
(no documents here)
3. winword.lnk
a. readme.doc
b. letter.docx
It seems it's a secreted info, because I cannot find any manual, any example of getting the list.
Related
I have a very big problem after migrating BPM from version 8.5.5 to BAW 22. I have a saved search on the process portal, which shows me the tasks of all users broken down by process. After migration, this search has stopped working and it only shows me my tasks and the team tasks I belong to. It stopped showing other users tasks. I tried to fix this error in different ways but nothing works. Can anyone help?
Can you provide more specifics on what you have tried so far?
Two things I would suggest:
If search optimization is enabled, check out this link here if you haven't already. You will need to drop the LSW_BPD_INSTANCE_VAR_NAMES and LSW_BPD_INSTANCE_VARS_PIVOT tables and recreate them using the steps mentioned here:
https://www.ibm.com/docs/en/baw/22.x?topic=portal-tuning-process-searches
2)Depending on your Saved Search criteria, it's possible you will need to re-create it. See the red alert section about existing saved searches and migration here:
https://www.ibm.com/docs/en/baw/22.x?topic=windows-restarting-verifying-migration.
It mentions 'earlier versions of Business Automation Workflow' but the same would apply to earlier versions of BPM
Using the exact example code given in the Google Drive APIs | Node.js Quickstart, the file information that is retrieved is not an accurate representation of the contents of my Google Drive. That is, even though there are 100+ filenames displayed, only one file (a folder) is actually on the 'My Drive' for my account!
Also I have then tried to 'filter' the files selected by using the query string (eg. "q: mimeType='image/jpeg'", and others), but it has no affect; the exact same results are returned.
Here is a truncated sample of the output. The 'Temporary' file is the folder which does exist in my account's "Google Drive 'My Drive'" but the others do not.
Files:
Temporary (17xAXYQzw0zYHpjeUP03sdx7qPd1Cnvv0)
Core Odd Years (0BxSZz46t09z1d0t1VWFkTkVkeWs)
Core Even Years (0BxSZz46t09z1ZTVVcm1lWEZvXzA)
Lesson Plans (1AhnLWyjBqtgTa-ofelROlZsnmzX1HiCl)
Hobbies (0BxSZz46t09z1ZkVQbTRiMTB1YTQ)
Hobbies-Steps-Overview.pdf (1E0E15rNOMCHV7OrjMCihjPK2yNLVpIdj)
Heritage (0BxSZz46t09z1cEpiWlYxWm1rNjA)
...
I expect that this is a well inspected example, so I'm unsure what could be the issue. Any help is appreciated.
If you are still looking for the solution, how about this answer? I think that 2 issues might be included in your situation.
About files which are not existing in your Google Drive.
The files might be the shared files.
In your question, you say that q cannot be used.
This might be due to the version of googleapis.
In order to confirm above issues, can you try the following 3 points?
For q, please try to use q: "'me' in owners".
This means that the files without sharing are displayed.
This is the same to sharedWithMe = false. Because sharedWithMe = false cannot be used, q: "'me' in owners" is used for this situation.
For q, please try to use q: "sharedWithMe".
This means that only the shared files are displayed.
Or please confirm "Shared with me" in your Google Drive using your browser.
If q: "'me' in owners" and q: "sharedWithMe" cannot be used for your environment, please confirm the version of googleapis for node.js.
If you are using no latest version, please update to the latest one. The current version is v28.0.1.
I confirmed that the sample script of quickstart can be used for v27.0.0 - v28.0.1.
Reference :
Search for Files
If my answer is not useful for you, I'm sorry.
In Xcode 7, is there a way to order the search results of the Open Quickly command?
The goal is to show Swift files first.
Apparently this is a known issue captured on the Apple Developer Forums. As of now, it doesn't appear possible to configure Xcode such that Swift files get listed first in the search results. Argh.
The best workaround as suggested in one of the posts is to leverage the fuzzy search algorithm in Xcode. That is, if you're searching for DirectoryViewController.swift, type dvc and that will list the Swift file first (presumably if there are no other project components named dvc).
I'm building a SP provider hosted app in Visual Studio. I just saw, that for each list I add to the project a new "Feature" is added, too. Can someone explain what the tasks of a feature are and how it is associated with the lists? Thank you!
You can see the feature as a container with yours SharePoint artefacts.
Basically, if you need to define a list, you'll have to create a definition list.
Then, you have to put this definition in a feature.
When your app'll be launched. The feature will be activated and the list inside your feature will be deployed on your site.
The features managment depends according to the developper. You can :
Put all in one feature. Sounds ok for small apps with one list.
Have one feature for the fields, on for the content type and one for the definition lists
Have one feature by fields/CT/list.
To separate lists will provide you more intel in case of error. You'll know that your specific feature in error manage a specific list. And you'll directly analyse what's wrong in your list. (Useful when the error is "An error has occured during the activation on the feature xxxx-xxxx-xxxx ... The log aren't everytime explicit)
In another hand, some developper'll tell that manage multiple features is an additional work. Up to you to weighing it up !
Note : In a SharePoint-hosted app, all the features are scoped web.
I am using VS.net and TFS. In the past I have stored my technical documentation (explanatory documents etc) in TFS document WSS repository and linked it to my source code via the Story, Task or other work item. This has proved unsatisfactory in the long term because the documentation is not strongly linked to the code it describes.
What options do I have to link documentation to code in VS.net/TFS other than through the work item. I can think of two options immediately -
1) Add it as Content to the project or solution itself and store it in the source code control repository
2) Add it as a URL in the code header, and store it in the TFS WSS document store.
Both these seem unsatisfactory - (1) means the documentation is not available outside the SCCS, and (2) means the programmer has to hunt through code to find the documentation link (which could be anywhere in any header).
Are there any other options that are in common use ?
Phillip
I don't know if there is a single golden answer to your question. But let me share how I do it.
Personally I split my documentation in technical and business documentation.
Technical documentation only consists of four documents:
What are we building, short document that you can give to a new developer to get quickly up to speed what the project is all about.
Instructions to compile. This document describes any steps a developer needs to take on a completely new machine to compile the code and run unit tests
Instructions to deploy. All necessary information to deploy the app to a new environment
Technologies. A list of technologies used in the project with links to more information if a developer needs to learn something.
This documentation is stored in a solution folder as part of the solution in Visual Studio.
Outside stakeholders can view this documentation through the web access of TFS. They can't change it however without having Visual Studio or Team Explorer and knowing how to use those.
For all other documentation we use SharePoint. TFS allows you to link Workitems to documents in SharePoint. We try to avoid any technical documentation in here.
Another option that you might consider is to create a new Work Item type called "document" and to have a hyperlink from here to the document location. Now you can create hard links between code files and changesets as well as PBI's to originating documentation.
In addition, when documents move you only have one place to update it.