Looking for the best practice here... I would like to allow multiple users to provide feedback against a single SketchFlow project. They would also like this ability so that they could see everyone else's annotations. I realize that they could very well do this now, but is there a way to distinguish what feedback belongs to a given user?
It seems to me that there are two possible solutions, both seem a bit kludgey:
Single .feedback file -- Ask users to each use their own color (i.e. Tom always uses red, Sally always uses blue, etc)...or, ask users to include their initials in their feedback statements.
Individual .feedback files -- Publish (copy) the SketchFlow project to individual folders, one folder for each user. While this would definitely distinguish user feedback, they would not be able to see other users' feedback.
It is amazing how fast technology evolves and improves! With the advent of the just-released (June 7, 2010) SketchFlow/Blend version 4 there is a much more elegant way to handle this. SketchFlow 3 followed the hub-and-spoke approach, where multiple reviewers could submit feedback, but only the designer could see them all. SketchFlow 4 lets you publish to SharePoint with one click, where all reviewers may now see each others' comments. The (minor) drawbacks, though, are two:
You must have SharePoint.
You must use a Silverlight prototype (not a WPF prototype).
For further reading, I direct you to these:
Expression evangelist Christian Schormann, Collaborative SketchFlow Feedback with SharePoint, June 6, 2010.
My just-published article Creating WPF Prototypes with SketchFlow, June 18, 2010. See the Managing Feedback section.
You are correct that those are the 2 current options.
Related
I want to somehow create a To Do list in PowerApps, that connects to Outlook Tasks. It is avaliable as a
data source in PowerApps, so should be possible.
I want it to be shareable. The new Microsoft To-Do app is not, so can't use that. At least not yet.
EDIT 2018-05-15: Rather go directly to the answer given here, than read the rest, if you want to make a shareable To Do list that integrates with Outlook Tasks!
There is already a To Do list template in PowerApps, but it is built on Wunderlist and I do not want this (because I can't
see how Wunderlist can connect to Outlook Tasks). Good thing is Wunderlist is shareable, though.
Nevertheless, I am trying to start with the Wunderlist template, and replace all Wunderlist calls with appropriate Outlook Tasks calls; e.g.
UpdateContext({MyList:Wunderlist.RetrieveLists()});;
with something like:
UpdateContext({MyList:OutlookTasks.GetAllTasks(...
Anyone gone through this is welcome to give a hint. I have scanned through the Internet for any instructions, or a book, but as always
I find nothing. But I know this is all so new yet.
Or else, is there another way to go?
I finally found a way to accomplish this. But no, the PowerApp way is not the easiest way to go (at least yet). I edited the title.
Better to use Planner and Outlook Tasks, and create a group in Microsoft Teams.
In Teams, you can easily add Planner to the tabs, and it at once gives you a To Do option. You can select exactly those people should see the list
(member of the team: all of them , some, or only yourself). It works well on the mobile, too.
At the time of this writing, an integration Planner - Outlook Tasks is not yet implemented
by Microsoft, so for now we can follow Avem Evolution's excellent videos (using Flow):
https://www.youtube.com/watch?v=FytBrdPHH-A
Matt Soseman's article is very useful too:
https://blogs.technet.microsoft.com/skypehybridguy/2017/08/30/microsoft-teams-using-planner-to-stay-organized/
I've been giving a really fun task at work,
I need to create a SharePoint app or some sort of list on sharepoint, where someone can nominee people from the company to win some sort of recognition then this will go out to a group of people that will approve if they "deserve the recognition".
this project was being work by a guy that left the company last Friday so basically I have a week to do something about it and I don't really know a lot about SharePoint.
I've done my research, and at first I went straight to the technical point of view where I would just basically code a connection to database, design the interface etc... but sharepoint has a really friendly user interface, uh, so friendly that sometimes I feel like I'm not capable of controlling it.
I was assigned a "technical" resource, this person supports SharePoint in the company however she doesn't have experience of creating custom applications or what else.
she teach me how to create a list and editing a form, adding columns to it. A easy way of doing it btw, the fields were connected to the internal database in the company so basically I didn't have to do anything technical at that point.
but then it came the complications/limitations for example I wasn't able to auto-fill information let's say if I would search the name of a person I would want to fill his last name, phone number organization automatically, I would also like to nominee more than 1 people for a single project.
I found out that you're able to open the form in InfoPath so I did it and then I was looking for developer tap option but it just disappear every time I open up the form.
I was also expecting for a tree view or a binding view of the internal database where some controls were connected but I wasn't able to find anything.
I can only use the SharePoint that's already up on the intranet of the company, I don't have access to databases, therefore I can't connect to them "directly" let's say from VStudio to map data back and forth.
I understand this may not be a very technical question this more of an advice to a fellow developer I develop generally for android.
is there a way of just going around this issue?
thanks and I appreciate whoever reads this.
David,
I don't think someone is ever going to have an issue like this, but I came to the conclusion that you need access to the sharepoint server and use VS inside the server in order to code the custom list and form, having the capability to connect to internal databases.
Please ask one question per post!
I've done my research, and at first I went straight to the technical
point of view where I would just basically code a connection to
database, design the interface etc...
For this, you do not need to use Sharepoint! Use MS SQL Server
she teach me how to create a list
If you have chosen to usу Sharepoint lists then they use нтвук the MS SQL Server for storing them...
I found out that you're able to open the form in InfoPath so I did it
and then I was looking for developer tap option but it just disappear
every time I open up the form.
Please check the answer to question "Custom Code is disabled on my form/(it is a workflow form of a sp list workflow process)/ any workaround?". That is, code behind is not available in Infopath for Sharepoint List Form, it is by design.
I recently had my app certified (first time!) but not automatically published. The game is Easter themed and hence I'd like it to appear in the new list over the Easter period. I need to know how best to achieve this.
According to many posts online, the 'new list' isn't sorted in order of release date but instead, in order of certification date, an automated system, the certifiers choice etc.
Thre are some theories here:
http://forums.create.msdn.com/forums/t/85466.aspx
https://stackoverflow.com/questions/6536557/first-time-game-shows-up-way-down-the-list-of-new-free-games-on-wp7-marketplace
Both of these posts are in 2011 and aren't conclusive.
Does anybody know what ACTUALLY happens?
Thank you for any reply.
In my experience, the new apps are changed once per day or in a similar fashion. Again, from experience, you can't do anything to ensure that your application is first. However, I have manually published applications after they have been tested and approved and they were listed in the 'new' category as if they were published that day.
Usually, don't worry because your app will be listed in the first 20 of that 'day' at least once and if you get - or set ;) - some high ratings people will see it.
I found this out the hard way. The plan was to release to a few small markets to get some feedback and then do an update and release to the USA. Well, once the game was released to the USA it was not considered new and did not go into the NEW GAME list. It retained the release date of the initial release to the small markets. And as such, I totally missed out on the new release spike that we all have come to love and enjoy.
Check out Alien Escape
Game Trailer http://www.youtube.com/watch?v=kWE6Dlk6xpc
I have some apps on marketplace already. I can talk from experience. The release after you have published will depend on countries and will delay without fully control. Also if you don't make any advertisement, it will not work with only "keywords on marketplace". I have solved by using my own Webservice and I flagged the app with "LOCKED" view. On EASTERN you can unlock the app by using your Webservice flag and immediately when the app starts, user can use it UNLOCKED.
No other solution is working in time usable way. But I fully like it to have my own app under full control. Also, I have added an "Code behind" for Testers to let them test the app before EASTERN.
Happy eastern
There is not official standard dealing with the layout of about boxes, which display the credits of a computer software and other information.
What should a good about box contain? And... is it okay to put an easter egg in?
(source: seasip.info)
I generally prefer to make tabbed "About" boxes. The first tab usually displays information about the application (name, version, copyright, etc.). The other tab is usually a log of changes with the most recent changes at the top.
Legal will want their copyright and stuff, marketing will want their branding (even though the user has already bought the product), the dev team will want their names up there in liquid crystal, but what do users need?
App name and version number. Users may need this to troubleshoot problems, perhaps while in contact with tech support or when using a knowledge base. Use a version number system such that this is all the user needs to specify their build. Version number is also needed for the users to know if they can upgrade.
A brief statement of what the app does (e.g., “Photograph and picture organizer.”). Users often end up with software for which they can’t guess the purpose. “About” is a logical place to tell the user what the app is about.
Put the above in conspicuous text at the top of About. Have a single OK button. Everything else that may be required by others in your company really isn’t of any interest to the user and can all be in “fine print.”
You could also include the web site or email for tech support if you can rely on that being stable for years, but usually users have this before going to the About box.
Easter eggs are fine if you think it’s appropriate to have a little fun in your app and your users lean towards the geeky side of things. Just make sure it isn’t something that will alarm a low-end user (or a future high-end developer; see: http://blogs.msdn.com/jensenh/archive/2005/10/20/483041.aspx).
Looking at a few examples of About boxes:
Name of the software
Name of the publisher/author
Copyright and licensing information
Version information
A nice logo
These days, it probably wouldn't hurt to have a way to directly go to the website for the software in the About box itself.
Microsoft's Windows Vista User Experience Guidelines tend to have useful information on designing good user interfaces. I wasn't able to find information specific to About boxes, but the section for Dialog Boxes may be somewhat relevant.
A team in my workplace actually has made the coolest About box ever:
Every time you open it, it displays a different simple game, with pictures of the dev. team (memory games, tic-tac-toe, sudoku, etc)
As for the About page content, that is the best place to have the version / release information so you can offer easy support.
I am using mine as the abstract description and a link to the legal pages and a credits page. If you have a website, its URL should be there as well -- might as well make that click-able into your own web-view browser to your big "Company About" page on your web server (don't launch a real browser, or the user just left your application).
Make it enjoyable to read but be concise. Avoid any scrolling or paging -- except to a completely different set of informational screens.
Also, let it be obvious and easy to dismiss.
By-the-way, if you add an easter egg to an app that is submitted to Apple Store, you have to disclose the sequence for Apple to 'test'; they promise to keep the sequence confidential. If they discover it later, which will make it back to them through forums, etc., then they will automatically pull it from the store.
I tend to add program name, version, company copyright, contact information, license information. I also add various variables for problem resolving. Winows version, servicepack, dll version if i use critical dll's etc. A large application icon. Sometimes I add an easter egg or some keycombo that launch parts of the program meant for debug and support purposes.
Present:
The product development is done in Visual Studio at the moment using .Net technologies, so it's important to stay in the same set of tools. Roles apart from developers are using spreadsheets, docs and diagramming tools, photoshop to do their work.
Future:
We want to build a workflow (a sequential process with roles, queues for action items, passing on info from one role to the other, approval etc) for a product development. The software product will be in enhancement stage forever, more the reason to establish this flow.
Typical users are designers, business analysts, content creators, developers, code reviewers, testers.
Let's say a new webpage needs to be developed. It will be,
thought about by the analyst in the
tool, will enter the information in
some format
a designer will use drag and drop to
build the page look, pass it over to
the
content creator, who will add
content(help text, hyperlinks, pure
text etc) to the page
a developer will check his queue to start
building logic around this page and
make it functional.
I am thinking about Visual Studio Isolated shell to be used as a tool framework mainly due to it's IDE capabilities et al, to build this. Has anyone worked on a similar set of requirements? Any patterns/solutions/ideas around how to go about this in the VS Shell paradigm?
Update: Visual Studio Team System is already being used by the developers and testers, but there is no customized workflow for them (& analysts, designers etc) available in TFS. Also Visual Studio is not the place for non-dev users that want to do things like, - define navigation flow, design the page elements etc.
Sounds exactly like Microsoft Visual Studio Team System.
I think there is a market for this product as I could not find anything close. There are disparate tools and products but no unified IDE like experience available and needs to be built on our own.
VS Isolated Shell 2010 is the starting point and platform on which this can be built. Needs several man months and may be years. However TFS ALM application lifecycle management has several overlaps of features with this idea, although not all, because it doesn't provide a customized experience per your custom workflow.
Jury is out, needs figuring out.