Confluence vs PowerApps

• QUICK How-to Guides that can be generated and share instantly
• One can subscribe to the pages and spaces and receive updates in the feed on their home page
• Automatic Email notifications of new updates in the Confluence area
• The platform integrates easily with other Atlassian platforms including third-party apps thus improving its reliability

Read full review

• Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
• We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
• The online learning resources and tutorials are helpful as well for those who are tech savvy.

Read full review

• Navigation. Similar to other Atlassian products, users have complained that aspects of Confluence are difficult to learn right away[.]
• An issue that users can face when using Confluence is attempting to edit a document while someone else is editing. Although users can access the document and save it, they are unable to see the changes happening in [real-time] that other users are implementing until they refresh their page. Some users have also noted that this can result in loss of edits.
• Another drawback of using Confluence is its specific organizational structure. All information is stored within one page or project, although the page is able to be broken up into sections, some users do not prefer this style. Users can use the ‘page tree’ on each page to organize the different elements of each project.

Read full review

• More complicated to understand in comparison with Nintex Forms.
• Complicated to find errors.
• Using PowerApps for SharePoint Forms is a bit complicated by setting up the start and load scenario with a lot of JavaScript.
• Load values, change them by code, and save them back could be easier. Actually quite complicated to handle a lot of variables.

Read full review

• We've gone from folders and folders of Word documents and PDFs into a single system with a search feature to bring all of our data together and trackable
• While onboarding took a bit longer for the company (to switch from a Word document centric mindset - to a web-based one), overall the company has embraced the features and power of Confluence within the working stack
• However, as costs continue to climb for the Atlassian product, we are forced to continue our evaluation of the product - with replacing it a remote possibility if it begins to outprice its usefulness to us.

Read full review

• It has given us a focal point for development. We now have the possibility of connecting to mobile and the default SharePoint online interface isn't always easy to manipulate. PowerApps has given us an opportunity to improve our user experience.
• An improved user experience has given us a better shot at compliance. When users don't fight the environment, they don't gravitate towards workarounds or non-compliance.
• As lists and libraries change, the platform scales pretty well.
• Having users with the capability to create their own forms and tools has dialed back the app dev need (there is a balance though) and distributed power to the process architects and people who actually need the solutions in the first place—much more efficient model of service delivery: self-service.

Read full review