Project Description

Let's make our daily work easier!

We use Salesforce for everything regarding opportunities, customers, and even our time tracking but this is not efficient and we are missing important tools like a pricing application with automated workflow validation. Salesforce UI is complicated, limited, slow, hard to customize, costs a lot, the dependency is too strong and we are not the masters of the data.

The goal of this project is to create a new web UI following Information Systems and software design best practices so that we can easily implement regularly features needed by the Sales organization and innovate based on customer data. It will rely on Salesforce API but with a low coupling.

Goal for this Hackweek

Create the applications and demonstrate 1+ use case (to be defined before the start of the week). Source code quality will be checked and follow every best practices (CI/CD, lint, Sonar, NeuVector, automated tests, Helm) and will run in a Kubernetes cluster managed by Rancher, secured by NeuVector!

Resources

Example (suggestion): https://github.com/devpro/sales-portal

Anyone would be welcome to join and it could be an opportunity to see how a development team may work (Agile methodology, PO/BA/SM/Dev/QA/Ops roles)

Looking for hackers with the skills:

salesforce development informationsystem backend frontend

This project is part of:

Hack Week 23

Activity

  • about 2 years ago: bthomas added keyword "frontend" to this project.
  • about 2 years ago: bthomas added keyword "salesforce" to this project.
  • about 2 years ago: bthomas added keyword "development" to this project.
  • about 2 years ago: bthomas added keyword "informationsystem" to this project.
  • about 2 years ago: bthomas added keyword "backend" to this project.
  • about 2 years ago: bthomas originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    openQA log viewer by mpagot

    Description

    *** Warning: Are You at Risk for VOMIT? ***

    Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?

    You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).

    This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."

    Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.

    No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")

    This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.

    image

    Goals

    Work on the existing POC openqa-log-visualizer and change it to something usable

    Resources

    openqa-log-visualizer


    openQA log viewer by mpagot

    Description

    *** Warning: Are You at Risk for VOMIT? ***

    Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?

    You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).

    This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."

    Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.

    No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")

    This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.

    image

    Goals

    Work on the existing POC openqa-log-visualizer and change it to something usable

    Resources

    openqa-log-visualizer